aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/mfd/wm8350-gpio.c
diff options
context:
space:
mode:
authorCharles Keepax <ckeepax@opensource.wolfsonmicro.com>2014-07-18 07:59:00 -0400
committerChanwoo Choi <cw00.choi@samsung.com>2014-07-22 21:07:42 -0400
commit17271f608bf818a13b2c235d45258311308d5b03 (patch)
treeb1d295ae8e78932249a7a0a364099b052bf744fe /drivers/mfd/wm8350-gpio.c
parent0a16ee633a83374a2bedbd6a057ab7d7e50a1d50 (diff)
extcon: arizona: Get MICVDD against extcon device
Previously we would do a regulator get against the main Arizona device to obtain the MICVDD regulator. Arizona is an MFD device and normally MICVDD will be supplied by one of its children (the arizona-micsupp regulator). As devres destruction for the MFD device will run after all its children have been destroyed, the regulator will be destroyed before devres calls regulator_put. This causes a warning from both the destruction of the child node, as the regulator is still open, and from the put of the regulator as the regulator device has already been destroyed. A simple fix here is to get the regulator against the extcon device itself such that devres runs when the child is destroyed. This has the additional benefit that if for some reason the extcon driver is unloaded the regulator reference won't hang around until the MFD is unloaded. Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
Diffstat (limited to 'drivers/mfd/wm8350-gpio.c')
0 files changed, 0 insertions, 0 deletions