linux-toradex.git/drivers/regulator, branch v3.10.62 Linux kernel for Apalis and Colibri modules regulator: arizona-ldo1: remove bypass functionality 2014-09-17T16:03:57+00:00 Nikesh Oswal nikesh@opensource.wolfsonmicro.com 2014-07-04T08:55:16+00:00 b2102aa9271a4ac6c20b516304c2c88ee1d1cc7b commit 5b919f3ebb533cbe400664837e24f66a0836b907 upstream. WM5110/8280 devices do not support bypass mode for LDO1 so remove the bypass callbacks registered with regulator core. Signed-off-by: Nikesh Oswal <nikesh@opensource.wolfsonmicro.com> Signed-off-by: Mark Brown <broonie@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
commit 5b919f3ebb533cbe400664837e24f66a0836b907 upstream.

WM5110/8280 devices do not support bypass mode for LDO1 so remove
the bypass callbacks registered with regulator core.

Signed-off-by: Nikesh Oswal <nikesh@opensource.wolfsonmicro.com>
Signed-off-by: Mark Brown <broonie@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
regulator: core: Replace direct ops->disable usage 2014-03-31T16:58:13+00:00 Markus Pargmann mpa@pengutronix.de 2014-02-20T16:36:04+00:00 0f79475d04f898d21397eb787a2cdf3aefffbbd6 commit 66fda75f47dc583f1c187556e9a2c082dd64f8c6 upstream. There are many places where ops->disable is called directly. Instead we should use _regulator_do_disable() which also handles gpio regulators. To be able to use the wrapper function from _regulator_force_disable(), I moved the _notifier_call_chain() call from _regulator_do_disable() to _regulator_disable(). This way, _regulator_force_disable() can use different flags for _notifier_call_chain() without calling it twice. Signed-off-by: Markus Pargmann <mpa@pengutronix.de> Signed-off-by: Mark Brown <broonie@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
commit 66fda75f47dc583f1c187556e9a2c082dd64f8c6 upstream.

There are many places where ops->disable is called directly. Instead we
should use _regulator_do_disable() which also handles gpio regulators.

To be able to use the wrapper function from _regulator_force_disable(),
I moved the _notifier_call_chain() call from _regulator_do_disable() to
_regulator_disable(). This way, _regulator_force_disable() can use
different flags for _notifier_call_chain() without calling it twice.

Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
Signed-off-by: Mark Brown <broonie@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
regulator: core: Replace direct ops->enable usage 2014-03-24T04:38:14+00:00 Markus Pargmann mpa@pengutronix.de 2014-02-20T16:36:03+00:00 783d444c6dbca17d2b15918ef6b30add2ba586b8 commit 30c219710358c5cca2f8bd2e9e547c6aadf7cf8b upstream. There are some direct ops->enable in the regulator core driver. This is a potential issue as the function _regulator_do_enable() handles gpio regulators and the normal ops->enable calls. These gpio regulators are simply ignored when ops->enable is called directly. One possible bug is that boot-on and always-on gpio regulators are not enabled on registration. This patch replaces all ops->enable calls by _regulator_do_enable. [Handle missing enable operations -- broonie] Signed-off-by: Markus Pargmann <mpa@pengutronix.de> Signed-off-by: Mark Brown <broonie@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
commit 30c219710358c5cca2f8bd2e9e547c6aadf7cf8b upstream.

There are some direct ops->enable in the regulator core driver. This is
a potential issue as the function _regulator_do_enable() handles gpio
regulators and the normal ops->enable calls. These gpio regulators are
simply ignored when ops->enable is called directly.

One possible bug is that boot-on and always-on gpio regulators are not
enabled on registration.

This patch replaces all ops->enable calls by _regulator_do_enable.

[Handle missing enable operations -- broonie]

Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
Signed-off-by: Mark Brown <broonie@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
mfd: tps6586x: correct device name of the regulator cell 2013-06-24T11:37:47+00:00 Marc Dietrich marvin24@gmx.de 2013-06-10T20:27:55+00:00 ec8da805c43a6cc0252dad0ff6e348c731e0b138 Change the device name of the regulator function to the one chosen for MODULE_ALIAS. This fixes kernel auto-module loading for the regulator function. Signed-off-by: Marc Dietrich <marvin24@gmx.de> Signed-off-by: Mark Brown <broonie@linaro.org> 
Change the device name of the regulator function to the one chosen for
MODULE_ALIAS. This fixes kernel auto-module loading for the regulator function.

Signed-off-by: Marc Dietrich <marvin24@gmx.de>
Signed-off-by: Mark Brown <broonie@linaro.org>
Merge remote-tracking branch 'regulator/fix/palmas' into regulator-linus 2013-05-30T10:58:40+00:00 Mark Brown broonie@opensource.wolfsonmicro.com 2013-05-30T10:58:40+00:00 dcbd8eec68500beed75cf41630b89da6c85ad1e4 






Merge remote-tracking branch 'regulator/fix/doc' into regulator-linus
2013-05-30T10:58:39+00:00

Mark Brown
broonie@opensource.wolfsonmicro.com

2013-05-30T10:58:39+00:00

2a66a854f5d716bb67e24dba78e53bdd5f0253ad












Merge remote-tracking branch 'regulator/fix/dbx500' into regulator-linus
2013-05-30T10:58:37+00:00

Mark Brown
broonie@opensource.wolfsonmicro.com

2013-05-30T10:58:37+00:00

e4bf063cb8b5e3648aa9917692b185068ab8ba23












regulator: palmas: Fix "enable_reg" to point to the correct reg for SMPS10
2013-05-30T10:55:55+00:00

Kishon Vijay Abraham I
kishon@ti.com

2013-05-30T10:25:09+00:00

f232168df0c7e7414b70ac5d8fed83086d441c0b

regulator_enable_regmap() uses enable_reg to enable the regulator.
But enable_reg for smps10 points to SMPS10_STATUS which is a
read-only register. Fixed the same by having enable_reg
set to SMPS10_CTRL.

Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: stable@vger.kernel.org





regulator_enable_regmap() uses enable_reg to enable the regulator.
But enable_reg for smps10 points to SMPS10_STATUS which is a
read-only register. Fixed the same by having enable_reg
set to SMPS10_CTRL.

Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: stable@vger.kernel.org







regulator: palmas: Fix incorrect condition
2013-05-30T10:55:46+00:00

Sachin Kamat
sachin.kamat@linaro.org

2013-05-08T10:39:06+00:00

3f4d6364084ca0525591836eba4a59f04bb85c68

Since 'id' cannot take two values at the same time, the condition
should probably be an OR (||) instead of AND (&&).

Introduced by commit 28d1e8cd67 ("regulator: palma: add ramp delay
support through regulator constraints").

Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>





Since 'id' cannot take two values at the same time, the condition
should probably be an OR (||) instead of AND (&&).

Introduced by commit 28d1e8cd67 ("regulator: palma: add ramp delay
support through regulator constraints").

Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>







regulator: core: Correct spelling mistake in comment
2013-05-21T15:35:40+00:00

Charles Keepax
ckeepax@opensource.wolfsonmicro.com

2013-05-21T14:04:07+00:00

ce0d10f887cabf9f16d1cbb60ef013021befbfdf

Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>





Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>