From: Christian Hewitt <christianshewitt@gmail.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Neil Armstrong <narmstrong@baylibre.com>,
devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: meson: remove CPU opps below 1GHz for G12B/SM1
Date: Thu, 10 Feb 2022 05:46:52 +0400 [thread overview]
Message-ID: <C70293C2-8CE8-42CE-911A-E0CC3DFB82FC@gmail.com> (raw)
In-Reply-To: <7h7da3o6cg.fsf@baylibre.com>
> On 10 Feb 2022, at 5:31 am, Kevin Hilman <khilman@baylibre.com> wrote:
>
> Christian Hewitt <christianshewitt@gmail.com> writes:
>
>> Amlogic G12B and SM1 devices experience CPU stalls and random board
>> wedges when the system idles and CPU cores clock down to lower opp
>> points. Recent vendor kernels include a change to remove 100-250MHz
>> (with no explanation) [0] but other downstream sources also remove
>> the 500/667MHz points (also with no explanation). Unless 100-667Mhz
>> opps are removed or the CPU governor forced to performance, stalls
>> are observed, so let's remove them an improve stability/uptime.
>
> Just curious: what CPUfreq governor do you use by default for the
> LibreELEC kernel?
LE uses ondemand. One of the original clues on the problem us that the
issue isn’t seen in some of the retro-gaming forks on LE's codebase
which use the performance governor (and overclocks, etc.)
> Your patch greatly improves the stability I'm seeing, but doesn't quite
> elimitate it.
>
> I'm testing suspend/resume in a loop on VIM3, and with schedutil
> (default) or ondemand, it eventually hangs. With either powersave or
> performance it's stable.
>
> Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2022-02-10 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 13:55 Christian Hewitt
2022-02-09 20:46 ` Kevin Hilman
2022-02-10 1:31 ` Kevin Hilman
2022-02-10 1:46 ` Christian Hewitt [this message]
2022-02-11 20:54 ` Kevin Hilman
2022-02-10 9:34 ` Neil Armstrong
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=C70293C2-8CE8-42CE-911A-E0CC3DFB82FC@gmail.com \
--to=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®