alistair23-linux/drivers/regulator
Stephen Boyd d92d95b6bf regulator: Fix recursive mutex lockdep warning
A recursive lockdep warning occurs if you call
regulator_set_optimum_mode() on a regulator with a supply because
there is no nesting annotation for the rdev->mutex. To avoid this
warning, get the supply's load before locking the regulator's
mutex to avoid grabbing the same class of lock twice.

=============================================
[ INFO: possible recursive locking detected ]
3.4.0 #3257 Tainted: G        W
---------------------------------------------
swapper/0/1 is trying to acquire lock:
 (&rdev->mutex){+.+.+.}, at: [<c036e9e0>] regulator_get_voltage+0x18/0x38

but task is already holding lock:
 (&rdev->mutex){+.+.+.}, at: [<c036ef38>] regulator_set_optimum_mode+0x24/0x224

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&rdev->mutex);
  lock(&rdev->mutex);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

3 locks held by swapper/0/1:
 #0:  (&__lockdep_no_validate__){......}, at: [<c03dbb48>] __driver_attach+0x40/0x8c
 #1:  (&__lockdep_no_validate__){......}, at: [<c03dbb58>] __driver_attach+0x50/0x8c
 #2:  (&rdev->mutex){+.+.+.}, at: [<c036ef38>] regulator_set_optimum_mode+0x24/0x224

stack backtrace:
[<c001521c>] (unwind_backtrace+0x0/0x12c) from [<c00cc4d4>] (validate_chain+0x760/0x1080)
[<c00cc4d4>] (validate_chain+0x760/0x1080) from [<c00cd744>] (__lock_acquire+0x950/0xa10)
[<c00cd744>] (__lock_acquire+0x950/0xa10) from [<c00cd990>] (lock_acquire+0x18c/0x1e8)
[<c00cd990>] (lock_acquire+0x18c/0x1e8) from [<c080c248>] (mutex_lock_nested+0x68/0x3c4)
[<c080c248>] (mutex_lock_nested+0x68/0x3c4) from [<c036e9e0>] (regulator_get_voltage+0x18/0x38)
[<c036e9e0>] (regulator_get_voltage+0x18/0x38) from [<c036efb8>] (regulator_set_optimum_mode+0xa4/0x224)
...

Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
2012-07-03 20:25:58 +01:00
..
88pm8607.c
aat2870-regulator.c
ab3100.c
ab8500.c regulator: Change ab8500 match names to reflect Device Tree 2012-06-17 18:27:47 +01:00
ad5398.c
anatop-regulator.c regulator: anatop: Use correct __devexit_p annotation 2012-06-04 10:42:49 +01:00
core.c regulator: Fix recursive mutex lockdep warning 2012-07-03 20:25:58 +01:00
da903x.c
da9052-regulator.c
db8500-prcmu.c regulator: Change db8500-prcmu match names to reflect Device Tree 2012-06-17 18:27:49 +01:00
dbx500-prcmu.c
dbx500-prcmu.h
dummy.c
dummy.h
fixed-helper.c
fixed.c
gpio-regulator.c regulator: gpio-regulator: populate selector from set_voltage 2012-06-04 10:44:30 +01:00
isl6271a-regulator.c
Kconfig
lp3971.c
lp3972.c
Makefile
max1586.c
max8649.c regulator: max8649: fix missing regmap in rdev 2012-06-05 11:15:22 +01:00
max8660.c
max8925-regulator.c
max8952.c
max8997.c regulator updates for 3.5 2012-05-21 16:49:16 -07:00
max8998.c
mc13xxx-regulator-core.c
mc13xxx.h
mc13783-regulator.c
mc13892-regulator.c
of_regulator.c
palmas-regulator.c regulator: palmas: fix regmap offsets for enable/disable 2012-06-23 11:37:28 +01:00
pcap-regulator.c
pcf50633-regulator.c
rc5t583-regulator.c
s5m8767.c regulator: Fix the s5m8767a problem of the division by null 2012-06-17 18:27:20 +01:00
tps6105x-regulator.c
tps6507x-regulator.c
tps6524x-regulator.c regulator: tps6524x: Fix get_voltage_sel for fixed voltage 2012-06-20 11:20:24 +01:00
tps6586x-regulator.c
tps62360-regulator.c regulator: tps62360: dt: initialize of_node param for regulator register. 2012-05-20 18:22:41 +01:00
tps65023-regulator.c regulator: tps65023: Fix mask for LDOs output voltage select control 2012-06-17 20:56:54 +01:00
tps65090-regulator.c
tps65217-regulator.c
tps65910-regulator.c MFD changes for 3.5 2012-05-29 11:53:11 -07:00
tps65912-regulator.c
twl-regulator.c
userspace-consumer.c
virtual.c
wm831x-dcdc.c MFD changes for 3.5 2012-05-29 11:53:11 -07:00
wm831x-isink.c MFD changes for 3.5 2012-05-29 11:53:11 -07:00
wm831x-ldo.c MFD changes for 3.5 2012-05-29 11:53:11 -07:00
wm8350-regulator.c
wm8400-regulator.c
wm8994-regulator.c