Re: [PATCH] mfd: madera: Improve handling of regulator unbinding
From: Lee Jones
Date: Mon Nov 11 2019 - 04:58:08 EST
On Tue, 05 Nov 2019, Charles Keepax wrote:
> The current unbinding process for Madera has some issues. The trouble
> is runtime PM is disabled as the first step of the process, but
> some of the drivers release IRQs causing regmap IRQ to issue a
> runtime get which fails. To allow runtime PM to remain enabled during
> mfd_remove_devices, the DCVDD regulator must remain available. In
> the case of external DCVDD's this is simple, the regulator can simply
> be disabled/put after the call to mfd_remove_devices. However, in
> the case of an internally supplied DCVDD the regulator needs to be
> released after all the MFD children, except for the regulator child
> itself, have been removed. This is achieved by having the regulator
> driver itself do the disable/put, as it is the last driver removed from
> the MFD.
>
> Signed-off-by: Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxx>
I'm fine with it, but Mark needs to review.
> ---
> drivers/mfd/madera-core.c | 20 ++++++++++++--------
> drivers/regulator/arizona-ldo1.c | 14 +++++++++++++-
> 2 files changed, 25 insertions(+), 9 deletions(-)
For my own reference:
Acked-for-MFD-by: Lee Jones <lee.jones@xxxxxxxxxx>
--
Lee Jones [æçæ]
Linaro Services Technical Lead
Linaro.org â Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog