linux-toradex.git/drivers/regulator, branch tegra-10.7.1

tegra gpio module: Using regulator module for GPIO power rail control

2010-06-26T16:55:02+00:00

Modify gpio module to use regulator module for controlling GPIO power rail.
Since there are some issues related to init sequence after this change, using
"postcore_initcall_sync" to involve regulator module, as well as modifying
NvRmOpenNew routine are required.

Bug Id 697774

Change-Id: Ie8002f1190da83355c0554496f9fef24d18207f5
Reviewed-on: http://git-master/r/3103
Reviewed-by: Gary King 
Tested-by: Gary King

regulator: tegra: add charger support to the tegra regulator driver

2010-05-28T05:23:26+00:00

add new fields to the platform data structure to allow specification of
chargers (current sources) vs regulators (voltage sources) on the platform

Change-Id: If4d0b2520a37afb96d103d6cbf78ec2fba2d02f9

regulator: tegra: add support for SoC power-off

2010-05-26T00:35:49+00:00

SoC power-off in the ODM PMU adaptation is triggered by requesting a
voltage of 0 for the voltage rails specified by the NV_VDD_SoC_ODM_ID
GUID. mark this regulator as enabled-on-boot.

Change-Id: I5b8b3df6176a5cd67b2041c328014291d6d0feb0

regulator: add tegra SoC regulator driver

2010-05-24T05:14:31+00:00

enables platform code to register ODM queriable GUIDs as named regulators,
and to specify the list of consumers for each registered regulator. uses
NvRm PMU API to program the PMU

Change-Id: I0cd04ad4bebc610d945daaf575f5d09e8d838385

regulator: Fix display of null constraints for regulators

2010-02-23T15:37:49+00:00

commit 973e9a2795b3b41d8408a0bb6f87b783c5efc88a upstream.

If the regulator constraints are empty and there is no voltage
reported then nothing will be added to the text displayed for the
constraints, leading to random stack data being printed. This is
unlikely to happen for practical regulators since most will at
least report a voltage but should still be fixed.

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood 
Signed-off-by: Greg Kroah-Hartman

regulator: Specify REGULATOR_CHANGE_STATUS for WM835x LED constraints

2010-02-09T12:50:53+00:00

commit a2fad9bf26a1d44a8d31a5c4528108a2b9f468ab upstream.

The WM8350 LED driver needs to be able to enable and disable the
regulators it is using. Previously the core wasn't properly enforcing
status change constraints so the driver was able to function but this
has always been intended to be required.

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood 
Signed-off-by: Greg Kroah-Hartman

regulator: Initialise wm831x structure pointor for ISINK driver

2009-12-02T19:37:16+00:00

The version that made it into mainline missed the initialisation of the
chip handle.

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood

dereferencing freed memory regulator_fixed_voltage_remove()

2009-11-16T12:40:25+00:00

Don't dereference drvdata after it has been freed.

regards,
dan carpenter

Signed-off-by: Dan Carpenter 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Fix check of unsigned return value and transmit errors in wm831x_gp_ldo_get_mode()

2009-11-16T09:57:17+00:00

If ret is unsigned, the checks for negative wm831x_reg_read() return values
are wrong. The error value should be transmitted to its caller, e.g.
wm831x_gp_ldo_get_status() which tests for a negative return value.

Signed-off-by: Roel Kluin 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Handle missing constraints in _regulator_disable()

2009-11-16T09:57:16+00:00

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood