Message ID | 20190827100307.21661-1-narmstrong@baylibre.com (mailing list archive) |
---|---|
Headers | show |
Series | arm64: dts: meson-g12: specify suspend OPP | expand |
Neil Armstrong <narmstrong@baylibre.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. Kevin
Kevin Hilman <khilman@baylibre.com> writes: > Neil Armstrong <narmstrong@baylibre.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