- 03 Jun, 2014 40 commits
-
-
Doug Anderson authored
On ARM Chromebooks we have a few devices that are accessed by both the AP (the main "Application Processor") and the EC (the Embedded Controller). These are: * The battery (sbs-battery). * The power management unit tps65090. On the original Samsung ARM Chromebook these devices were on an I2C bus that was shared between the AP and the EC and arbitrated using some extranal GPIOs (see i2c-arb-gpio-challenge). The original arbitration scheme worked well enough but had some downsides: * It was nonstandard (not using standard I2C multimaster) * It only worked if the EC-AP communication was I2C * It was relatively hard to debug problems (hard to tell if i2c issues were caused by the EC, the AP, or some device on the bus). On the HP Chromebook 11 the design was changed to: * The AP/EC comms were still i2c, but the battery/tps65090 were no longer on the bus used for AP/EC communication. The battery was exposed to the AP through a limited i2c tunnel and tps65090 was exposed to the AP through a custom Linux driver. On the Samsung ARM Chromebook 2 the scheme is changed yet again, now: * The AP/EC comms are now using SPI for faster speeds. * The EC's i2c bus is exposed to the AP through a full i2c tunnel. The upstream "tegra124-venice2" uses the same scheme as the Samsung ARM Chromebook 2, though it has a different set of components on the other side of the bus. This driver supports the scheme used by the Samsung ARM Chromebook 2. Future patches to this driver could add support for the battery tunnel on the HP Chromebook 11 (and perhaps could even be used to access tps65090 on the HP Chromebook 11 instead of using a special driver, but I haven't researched that enough). Signed-off-by:
Vincent Palatin <vpalatin@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Doug Anderson <dianders@chromium.org> Reviewed-by:
Wolfram Sang <wsa@the-dreams.de> Signed-off-by:
Lee Jones <lee.jones@linaro.org>
-
Bill Richardson authored
This just updates include/linux/mfd/cros_ec_commands.h to match the latest EC version (which is the One True Source for such things). See <https://chromium.googlesource.com/chromiumos/platform/ec> [dianders: took today's ToT version from the Chromium OS EC; deleted references to cros_ec_dev and cros_ec_lpc since those aren't upstream yet] Signed-off-by:
Bill Richardson <wfrichar@chromium.org> Signed-off-by:
Andrew Bresticker <abrestic@chromium.org> Tested-by:
Stephen Warren <swarren@nvidia.com> Signed-off-by:
-
Doug Anderson authored
We're adding i2c tunneling to the list of things that goes over cros_ec. i2c tunneling can be slooooooow, so increase our deadline to 100ms to account for that. Signed-off-by:
-
Doug Anderson authored
The cros_ec_spi transfer had two problems with its timeout code: 1. It looked at the timeout even in the case that it found valid data. 2. If the cros_ec_spi code got switched out for a while, it's possible it could get a timeout after a single loop. Let's be paranoid and make sure we do one last transfer after the timeout expires. Signed-off-by:
-
Doug Anderson authored
The main transfer function for cros_ec_spi can be called by more than one client at a time. Make sure that those clients don't stomp on each other by locking the bus for the duration of the transfer function. Signed-off-by:
-
David Hendricks authored
To avoid spamming the EC we calculate the time between the previous transfer and the current transfer and force a delay if the time delta is too small. However, a small miscalculation causes the delay period to be far too short. Most noticably this impacts commands with a long turnaround time such as EC firmware reads and writes. Signed-off-by:
David Hendricks <dhendrix@chromium.org> Signed-off-by:
-
Charles Keepax authored
Signed-off-by:
Charles Keepax <ckeepax@opensource.wolfsonmicro.com> Signed-off-by:
-
Charles Keepax authored
Some output configurations can require a 50Mhz SYSCLK which requires DCVDD to be 1.8V. This patch adds the registers necessary for supporting this operational mode. Signed-off-by:
-
Charles Keepax authored
Currently, MICVDD only binds because it is both the regulator name and the consumer name and we will always match against the regulator name regardless of the consumer device. If the regulator was renamed using the init_data ASoC will no longer be able to locate the supply, as it will be looking on the CODEC device where as the MICVDD consumer is on the Arizona device. Add a mapping as we do for the other regulators. Signed-off-by:
-
Krzysztof Kozlowski authored
mfd_add_devices() expects array of struct mfd_cell to be const. Signed-off-by:
Krzysztof Kozlowski <k.kozlowski@samsung.com> Acked-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Jingoo Han authored
Use devm_ioremap_resource() because devm_request_and_ioremap() is obsoleted by devm_ioremap_resource(). Signed-off-by:
Jingoo Han <jg1.han@samsung.com> Acked-by:
-
Linus Walleij authored
This adds a driver for the Atmel Microcontroller found on the iPAQ h3xxx series. This device handles some keys, the touchscreen, and the battery monitoring. This is a port of a driver from handhelds.org 2.6.21 kernel, written by Alessandro Gardich based on Andrew Christians original HAL-driver. It has been heavily cleaned and converted to mfd-core by Dmitry Artamonow and rewritten again for the v3.x series kernels by Linus Walleij, bringing back some of the functionality lost from Andrew's original driver. Acked-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
Alessandro Gardich <gremlin@gremlin.it> Signed-off-by:
Dmitry Artamonow <mad_soft@inbox.ru> Signed-off-by:
-
Tushar Behera authored
commit df73de9b ("mfd: syscon: Return -ENOSYS if CONFIG_MFD_SYSCON is not enabled") introduced fallbacks for APIs, but missed out on adding the header file. This would work only if linux/err.h is also included in the source code from where this file is included. It would be better to include linux/err.h in file to remove possible build errors. Without this patch, we get following and similar build errors if this header file is included in some source file and CONFIG_MFD_SYSCON is not enabled. include/linux/mfd/syscon.h: In function ‘syscon_node_to_regmap’: include/linux/mfd/syscon.h:30:2: error: implicit declaration of function ‘ERR_PTR’ [-Werror=implicit-function-declaration] return ERR_PTR(-ENOSYS); ^ include/linux/mfd/syscon.h:30:18: error: ‘ENOSYS’ undeclared (first use in this function) return ERR_PTR(-ENOSYS); ^ Signed-off-by:
Tushar Behera <tushar.behera@linaro.org> Signed-off-by:
-
Boris BREZILLON authored
The PRCM (Power/Reset/Clock Management) block exposes several subdevices in different subsystems (clk, reset ...) Add basic support for the PRCM unit with clk (AR100, AHB0, and APB0 clks) and reset controller subdevices. Other subdevices might be added later (if needed). Signed-off-by:
Boris BREZILLON <boris.brezillon@free-electrons.com> Acked-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Signed-off-by:
-
Boris BREZILLON authored
Document DT bindings of the PRCM (Power/Reset/Clock Management) unit. Signed-off-by:
-
Krzysztof Kozlowski authored
mfd_add_devices() expects array of struct mfd_cell to be const. Signed-off-by:
Roger Tseng <rogerable@realtek.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id may be be const as expected by of_platform_populate() call. Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id may be be const as expected by of_match_table field. Signed-off-by:
-
Krzysztof Kozlowski authored
mfd_add_devices() expects array of struct mfd_cell to be const. Signed-off-by:
-
Krzysztof Kozlowski authored
mfd_add_devices() expects array of struct mfd_cell to be const. Signed-off-by:
Milo Kim <milo.kim@ti.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id should be const as expected by both of_match_table field and of_match_device() call. Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id may be be const as expected by both of_match_table field and of_match_node() call. Signed-off-by:
-
Krzysztof Kozlowski authored
mfd_add_devices() expects array of struct mfd_cell to be const. Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id may be be const as expected by both of_match_table field and of_match_node() call. Signed-off-by:
-
Krzysztof Kozlowski authored
mfd_add_devices() expects array of struct mfd_cell to be const. Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id may be be const as expected by of_match_table field. Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id may be be const as expected by of_match_table field. Signed-off-by:
Chanwoo Choi <cw00.choi@samsung.com> Signed-off-by:
-
Krzysztof Kozlowski authored
The kempld_devs (array of mfd_cells) can be safely made const. Signed-off-by:
Kevin Strasser <kevin.strasser@linux.intel.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id may be be const as expected by both of_match_table field and of_match_node() call. Signed-off-by:
-
Krzysztof Kozlowski authored
Array of struct of_device_id may be be const as expected by of_match_table field. Signed-off-by:
-
Alexander Shiyan authored
This patch removes platform data usage for codec and touchscreen when driver is used with devicetree. This fixes possible "null pointer dereference" error if DTS uses "fsl,mc13xxx-uses-codec" or "fsl,mc13xxx-uses-touch" options. Signed-off-by:
Alexander Shiyan <shc_work@mail.ru> Signed-off-by:
-
Peter Ujfalusi authored
When the MCLK is 19.2 or 38.4 MHz the HPPLL need to be enabled and can be put in bypass mode. This will fix HPPLL use on boards with 19.2MHz mclk. Signed-off-by:
Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by:
-
Jingoo Han authored
Make of_device_id array const, because all OF functions handle it as const. Signed-off-by:
-
Jingoo Han authored
Make of_device_id array const, because all OF functions handle it as const. Signed-off-by:
-
Jingoo Han authored
Make of_device_id array const, because all OF functions handle it as const. Signed-off-by:
-
Jingoo Han authored
Make of_device_id array const, because all OF functions handle it as const. Signed-off-by:
-
Carlo Caione authored
This patch introduces the preliminary support for PMICs X-Powers AXP202 and AXP209. The AXP209 and AXP202 are the PMUs (Power Management Unit) used by A10, A13 and A20 SoCs and developed by X-Powers, a sister company of Allwinner. The core enables support for two subsystems: - PEK (Power Enable Key) - Regulators Signed-off-by:
Carlo Caione <carlo@caione.org> Signed-off-by:
-
Pankaj Dubey authored
If we pass syscon device node itself as first parameter to this function there is no need to parse and find syscon device node. So by allowing "property" parameter as NULL allow syscon_regmap_lookup_by_phandle to consider passed argument "np" itself as a syscon device node "syscon_np". This will help us in avoiding addition of "syscon" property in a device node which points back to same device node in device tree. Signed-off-by:
Pankaj Dubey <pankaj.dubey@samsung.com> Signed-off-by:
-
Stephen Boyd authored
The pm8xxx read/write wrappers are no longer necessary now that all the sub-device drivers are using the regmap API. Remove it. Signed-off-by:
Stephen Boyd <sboyd@codeaurora.org> Signed-off-by:
-
Krzysztof Kozlowski authored
During suspend the IRQ should be disabled even if this is not a wakeup source. This is a proper way of fixing the IRQ handling issue during resume (IRQ handler fails because I2C bus did not resume yet). When device is suspended and max14577 interrupt is signaled the irq chip will try to handle it regardless of wakeup source. Device could be woken up by different IRQ but still the IRQ handler will try to read the registers over I2C bus and fail because I2C bus won't be ready yet: max14577 2-0025: Failed to read IRQ status: -5 Signed-off-by:
-
