- 03 Jun, 2014 37 commits
-
-
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:
Lee Jones <lee.jones@linaro.org>
-
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 <jg1.han@samsung.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:
-
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:
-
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 sec-core 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. Signed-off-by:
-
Krzysztof Kozlowski authored
The device type was stored in sec_pmic_dev state container twice: - unsigned long type (initialized from of_device_id or i2c_device_id) - int device_type (initialized as above or from board files when there is no DTS) The 'type' field was never used outside of probe so it can be safely removed. Change also the device_type in sec_pmic_dev and sec_platform_data to unsigned long to avoid any casts. Signed-off-by:
-
Peter Ujfalusi authored
Make sure that we patch the ACCCTL register as the first thing when the driver loads, thus configuring I2C fast mode and i2c access for dual access registers. Signed-off-by:
-
Peter Ujfalusi authored
In certain boards the source for the clk32k clock can be gated. In these boards the clk32k clock can be provided to the driver and it is going to be enabled/disabled when it is needed. If the clk32k clock is not provided the driver will assume that it is always running. Signed-off-by:
-
Peter Ujfalusi authored
All boards using twl6040 configures the i2c bus to 400KHz. While twl6040's defaults to normal mode (100KHz). So far twl6040 has no problem with i2c communication in this configuration it is safer to select fast i2c mode. Signed-off-by:
-
Peter Ujfalusi authored
If for some reason the boot loader enabled the audpwron GPIO we will have pending IRQs to be handled. This seams to break twl6040 for some reason leading to non working i2c communication (i2c timeouts). Clearing the INTID register after we requested the audpwron GPIO (and set it to low) will ensure that the chip will operate normally in this case as well. Signed-off-by:
-
Charles Keepax authored
The supply aliases for the MFD devices were being added using devres but the device hasn't been added at this point and as such we can't use devres. The MFD already has a function that removes devices this patch uses the non-devres versions of the supply alias functions and adds an unregister in mfd_remove_devices_fn. Reported-by:
Mark Brown <broonie@kernel.org> Signed-off-by:
Charles Keepax <ckeepax@opensource.wolfsonmicro.com> Reviewed-by:
-
Axel Lin authored
The valid gpio is GPIO0 ~ GPIO58, so ngpio should be 59. This patch also renames RDC321X_MAX_GPIO to RDC321X_NUM_GPIO because it actually means the number of available GPIOs. Signed-off-by:
Axel Lin <axel.lin@ingics.com> Acked-by:
-
Krzysztof Kozlowski authored
Update the documentation for sec_pmic state container structure to reflect current code. Signed-off-by:
-
Krzysztof Kozlowski authored
The rtc-s5m driver does not support all of S2M and S5M chipsets supported by main MFD sec-core driver. For such chipsets unsupported by rtc-s5m, the MFD sec-core driver initialized regmap with default config. This config in such cases wouldn't work at all. The main MFD sec-core driver shouldn't initialize regmap for child drivers which is not used by them and even not valid. Move the allocation of RTC I2C dummy device and initialization of RTC regmap from main MFD sec-core driver to the rtc-s5m driver. The rtc-s5m driver will use proper regmap config for supported devices. Signed-off-by:
Alessandro Zummo <a.zummo@towertech.it> Signed-off-by:
-
Bill Richardson authored
This module has always been GPL licensed. It was just missing the explicit declaration to avoid tainting the kernel. Signed-off-by:
Bill Richardson <wfrichar@chromium.org> Signed-off-by:
Doug Anderson <dianders@chromium.org> Signed-off-by:
-
Guenter Roeck authored
Panther Point PCH GPIO configuration is similar to V5 PCHs. Signed-off-by:
Guenter Roeck <linux@roeck-us.net> Signed-off-by:
-
Charles Keepax authored
The isolation control register is required when DCVDD is externally supplied add this in as a readable register. Signed-off-by:
-
Axel Lin authored
The *rdev[] is not used since commit 413be59e "regulator: tps65218: Remove unnecessary regulator_unregister call". Signed-off-by:
-
Fabio Estevam authored
After request_threaded_irq() is called there is a chance that an interrupt may occur before the 'mc13xxx->lock' is initialized, which will trigger a kernel oops. In order to prevent that, move the initialization of 'mc13xxx->lock' prior to requesting the interrupts. Suggested-by:
Russell King <rmk+kernel@arm.linux.org.uk> Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Acked-by:
-
Alexander Shiyan authored
Signed-off-by:
-
Jay Aurabind authored
On systems with CONFIG_FRAME_WARN=1024, compiler warns the allocation of an object of struct device on stack. Make the allocation dynamically to fix the warning. Also change the caller's return type to int so as to account for error handling. drivers/mfd/abx500-core.c: In function ‘abx500_dump_all_banks’: drivers/mfd/abx500-core.c:167:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=] Signed-off-by:
Aurabindo J <mail@aurabindo.in> Signed-off-by:
-
Michael Brunner authored
This patch adds attributes to the Kontron PLD driver to allow applications to retrieve firmware information. Additionally the format has been changed to conform with the representation in other Kontron software. Signed-off-by:
Michael Brunner <michael.brunner@kontron.com> Reviewed-by:
-
Axel Lin authored
This is a i2c driver, so uses i2c prefix in modalias. Signed-off-by:
-
Axel Lin authored
Add missing mfd_remove_devices() call in remove function. Signed-off-by:
-
Lee Jones authored
Merge branches 'ib-from-asoc-3.16', 'ib-from-pm-3.16', 'ib-from-regulator-3.16', 'ib-mfd-gpio-3.16' and 'ib-mfd-mmc-memstick-3.16', tags 'ib-mfd-extcon-3.16', 'ib-mfd-omap-3.16' and 'ib-mfd-regulator-3.16' into ibs-for-mfd-merged
-
- 27 May, 2014 1 commit
-
-
Lee Jones authored
regulator: Support newer revisions of tps658640 There are two different variants of the tps658640 with slightly different feature sets.
-
- 26 May, 2014 2 commits
-
-
Alban Bedel authored
The TPS658640 has a different set of output voltage for most LDO and the RTC LDO isn't settable. This chip also report 2 different version ID, as the datasheet doesn't list the possible values the second ID has simply been named TPS658640v2. Signed-off-by:
Alban Bedel <alban.bedel@avionic-design.de> Signed-off-by:
Mark Brown <broonie@linaro.org>
-
Alban Bedel authored
Add the required definitions and macros to allow easily adding fixed regulators. This required for the TPS658640 that doesn't allow setting the LDO_RTC output voltage. Signed-off-by:
-
