[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4aa88f7c-f1ea-4ab7-a806-3214c541ce7d@sirena.org.uk>
Date: Thu, 20 Apr 2023 15:50:39 +0100
From: Mark Brown <broonie@...nel.org>
To: Benjamin Bara <bbara93@...il.com>
Cc: mazziesaccount@...il.com, DLG-Adam.Ward.opensource@...renesas.com,
benjamin.bara@...data.com, lgirdwood@...il.com,
linux-kernel@...r.kernel.org, support.opensource@...semi.com
Subject: Re: [PATCH RFC 1/2] regulator: introduce regulator monitoring
constraints
On Thu, Apr 20, 2023 at 04:29:24PM +0200, Benjamin Bara wrote:
> On Thu, 20 Apr 2023 at 13:33, Matti Vaittinen <mazziesaccount@...il.com> wrote:
> > It would also allow drivers to add delays to the function(s)
> > re-enabling of monitors when needed - at least the bd718x7 had to wait
> > for new voltage to stabilize prior re-enabling the monitors.
> Also not 100% sure about this one, but I think these cases could be
> covered by a mandatory regulator-*-ramp-delay, when necessary?
If the voltage is out of spec there should be a ramp delay anyway, yes.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists