[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7ha7brrfe7.fsf@baylibre.com>
Date: Thu, 29 Aug 2019 11:32:48 -0700
From: Kevin Hilman <khilman@...libre.com>
To: Neil Armstrong <narmstrong@...libre.com>
Cc: linux-amlogic@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Neil Armstrong <narmstrong@...libre.com>
Subject: Re: [PATCH 0/3] arm64: dts: meson-g12: specify suspend OPP
Kevin Hilman <khilman@...libre.com> writes:
> Neil Armstrong <narmstrong@...libre.com> writes:
>
>> Tag the 1,2GHz OPP as suspend OPP to be set before going in suspend mode,
>> for the G12A, G12B and SM1 SoCs.
>>
>> It has been reported that using various OPPs can lead to error or
>> resume with a different OPP from the ROM, thus use this safe OPP as
>> it is the default OPP used by the BL2 boot firmware.
>>
>> Neil Armstrong (3):
>> arm64: dts: meson-g12a: specify suspend OPP
>> arm64: dts: meson-sm1: specify suspend OPP
>> arm64: dts: meson-g12b: specify suspend OPP
>
> Queued patches 1, 3 for v5.4.
>
> The SM1 patch has a dependency on the SM1 DVFS series, which in turn has
> a dependency on clock changes. Once I get a stable tag for the SM1
> clock changes, I'll queue up the rest.
FYI... I decided not to queue these for v5.4.
I'm pretty sure we'll need these, but I I think we need to do a bit more
suspend/resume testing to be sure we have the right OPPs. here.
For now, this series is in my `v5.4/testing` branch, which is included
in `integ` so it can get a bit broader testing.
Kevin
Powered by blists - more mailing lists