On Fri, Feb 12, 2016 at 08:24:11PM +0100, Paul Kocialkowski wrote:
> So I think the question here is why runtime pm is calling the device
> functions in reverse order. Any clue? Is that intended behavior?
Definitely not intended behaviour...
signature.asc
Description: PGP signature
Hi,
Le mardi 09 février 2016 à 21:51 +0100, Paul Kocialkowski a écrit :
> Le jeudi 21 janvier 2016 à 20:24 +, Mark Brown a écrit :
> > Provide a flag auto_runtime_pm in the regulator_desc which causes the
> > regulator core to take a runtime PM reference to a regulator while it
> > is enabled.
Hi,
Le jeudi 21 janvier 2016 à 20:24 +, Mark Brown a écrit :
> Provide a flag auto_runtime_pm in the regulator_desc which causes the
> regulator core to take a runtime PM reference to a regulator while it
> is enabled. This helps integration with chip wide power management for
> auxiliary PMIC
Le jeudi 21 janvier 2016 à 20:24 +, Mark Brown a écrit :
> Provide a flag auto_runtime_pm in the regulator_desc which causes the
> regulator core to take a runtime PM reference to a regulator while it
> is enabled. This helps integration with chip wide power management
> for
> auxiliary PMICs,
Hi Mark,
[auto build test WARNING on regulator/for-next]
[also build test WARNING on v4.4 next-20160121]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Mark-Brown/regulator-core-Use-a-bitfield
5 matches
Mail list logo
