[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191008124736.GJ4382@sirena.co.uk>
Date: Tue, 8 Oct 2019 13:47:36 +0100
From: Mark Brown <broonie@...nel.org>
To: Marek Szyprowski <m.szyprowski@...sung.com>
Cc: linux-kernel@...r.kernel.org, Dmitry Osipenko <digetx@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Lucas Stach <l.stach@...gutronix.de>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
linux-samsung-soc@...r.kernel.org,
Viresh Kumar <viresh.kumar@...aro.org>,
Kamil Konieczny <k.konieczny@...sung.com>
Subject: Re: [PATCH] regulator: core: Skip balancing of the enabled
regulators in regulator_enable()
On Tue, Oct 08, 2019 at 02:38:55PM +0200, Marek Szyprowski wrote:
> Then if I get it right, the issue is caused by the commit 7f93ff73f7c8
> ("opp: core: add regulators enable and disable"). I've checked and
> indeed reverting it fixes Peach Pi to boot properly. The question is if
> this is desired behavior or not?
That doesn't seem ideal - either it's redundant for regulators that need
to be marked as always-on anyway or it's going to force the regulators
on when a device could do runtime PM (eg, if the same code can run on
something like a GPU which can be turned off while the screen is off or
is displaying a static image).
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists