From: Kevin Hilman <khilman@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Neil Armstrong <narmstrong@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>
Subject: Re: [PATCH] arm64: dts: meson: remove CPU opps below 1GHz for G12B/SM1
Date: Wed, 09 Feb 2022 17:31:11 -0800 [thread overview]
Message-ID: <7h7da3o6cg.fsf@baylibre.com> (raw)
In-Reply-To: <20220209135535.29547-1-christianshewitt@gmail.com>
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?
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
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Neil Armstrong <narmstrong@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>
Subject: Re: [PATCH] arm64: dts: meson: remove CPU opps below 1GHz for G12B/SM1
Date: Wed, 09 Feb 2022 17:31:11 -0800 [thread overview]
Message-ID: <7h7da3o6cg.fsf@baylibre.com> (raw)
In-Reply-To: <20220209135535.29547-1-christianshewitt@gmail.com>
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?
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-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Neil Armstrong <narmstrong@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>
Subject: Re: [PATCH] arm64: dts: meson: remove CPU opps below 1GHz for G12B/SM1
Date: Wed, 09 Feb 2022 17:31:11 -0800 [thread overview]
Message-ID: <7h7da3o6cg.fsf@baylibre.com> (raw)
In-Reply-To: <20220209135535.29547-1-christianshewitt@gmail.com>
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?
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
next prev parent reply other threads:[~2022-02-10 1:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 13:55 [PATCH] arm64: dts: meson: remove CPU opps below 1GHz for G12B/SM1 Christian Hewitt
2022-02-09 13:55 ` Christian Hewitt
2022-02-09 13:55 ` Christian Hewitt
2022-02-09 20:46 ` Kevin Hilman
2022-02-09 20:46 ` Kevin Hilman
2022-02-09 20:46 ` Kevin Hilman
2022-02-10 1:31 ` Kevin Hilman [this message]
2022-02-10 1:31 ` Kevin Hilman
2022-02-10 1:31 ` Kevin Hilman
2022-02-10 1:46 ` Christian Hewitt
2022-02-10 1:46 ` Christian Hewitt
2022-02-10 1:46 ` Christian Hewitt
2022-02-11 20:54 ` Kevin Hilman
2022-02-11 20:54 ` Kevin Hilman
2022-02-11 20:54 ` Kevin Hilman
2022-02-10 9:34 ` Neil Armstrong
2022-02-10 9:34 ` Neil Armstrong
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=7h7da3o6cg.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.