From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH 0/3] arm64: dts: meson-g12: specify suspend OPP
Date: Thu, 29 Aug 2019 11:32:48 -0700 [thread overview]
Message-ID: <7ha7brrfe7.fsf@baylibre.com> (raw)
In-Reply-To: <7hy2zeuv9z.fsf@baylibre.com>
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
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-08-29 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 10:03 [PATCH 0/3] arm64: dts: meson-g12: specify suspend OPP Neil Armstrong
2019-08-27 10:03 ` [PATCH 1/3] arm64: dts: meson-g12a: " Neil Armstrong
2019-08-27 10:03 ` [PATCH 2/3] arm64: dts: meson-sm1: " Neil Armstrong
2019-08-27 10:03 ` [PATCH 3/3] arm64: dts: meson-g12b: " Neil Armstrong
2019-08-27 21:56 ` [PATCH 0/3] arm64: dts: meson-g12: " Kevin Hilman
2019-08-29 18:32 ` Kevin Hilman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ha7brrfe7.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).