[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9bea64d5-8689-48f0-a081-5da60434e6c0@sirena.org.uk>
Date: Fri, 22 Dec 2023 12:24:01 +0000
From: Mark Brown <broonie@...nel.org>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: lgirdwood@...il.com,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
linux-pwm@...r.kernel.org, linux-amlogic@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Thierry Reding <thierry.reding@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Dmitry Rokosov <ddrokosov@...rdevices.ru>
Subject: Re: [RFC PATCH v1] regulator: pwm-regulator: Fix continuous
get_voltage for disabled PWM
On Thu, Dec 21, 2023 at 11:42:29PM +0100, Martin Blumenstingl wrote:
> The vendor BSP includes a custom u-boot with lots of relevant
> information for which there's seemingly no documentation.
> It seems that 1.1V is what should be used during normal operation.
> 0.86V is what can be used during system suspend (when power to the
> Cortex-A5 cores is turned off and an integrated ARC core is taking
> over for wakeup purposes).
> Hence the supported voltage range of 0.86..1.1V
That sounds like the constraints are wrong actually, if 0.86V can only
be used during system suspend then it shouldn't be in the valid voltage
range - the suspend voltage doesn't need to be in the range used during
normal operation. If we might use it during runtime suspend then it
does need to be there though.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists