From: Benjamin Schneider <bschnei@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Benjamin Schneider <ben@bens.haus>
Subject: [PATCH] cpufreq: enable 1200Mhz clock speed for armada-37xx
Date: Sun, 2 Jun 2024 18:26:38 -0700 [thread overview]
Message-ID: <20240603012804.122215-2-ben@bens.haus> (raw)
In-Reply-To: <20240603012804.122215-1-ben@bens.haus>
This frequency was disabled because of unresolved stability problems.
However, based on several months of testing, the source of the
stability problems seems to be the bootloader, not the kernel.
Marvell has recently merged changes to their bootloader source that
addresses the stability issues when frequency scaling is enabled at
all frequencies including 1.2Ghz.
Signed-off-by: Benjamin Schneider <ben@bens.haus>
---
drivers/cpufreq/armada-37xx-cpufreq.c | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/cpufreq/armada-37xx-cpufreq.c b/drivers/cpufreq/armada-37xx-cpufreq.c
index bea41ccab..f28a4435f 100644
--- a/drivers/cpufreq/armada-37xx-cpufreq.c
+++ b/drivers/cpufreq/armada-37xx-cpufreq.c
@@ -102,11 +102,7 @@ struct armada_37xx_dvfs {
};
static struct armada_37xx_dvfs armada_37xx_dvfs[] = {
- /*
- * The cpufreq scaling for 1.2 GHz variant of the SOC is currently
- * unstable because we do not know how to configure it properly.
- */
- /* {.cpu_freq_max = 1200*1000*1000, .divider = {1, 2, 4, 6} }, */
+ {.cpu_freq_max = 1200*1000*1000, .divider = {1, 2, 4, 6} },
{.cpu_freq_max = 1000*1000*1000, .divider = {1, 2, 4, 5} },
{.cpu_freq_max = 800*1000*1000, .divider = {1, 2, 3, 4} },
{.cpu_freq_max = 600*1000*1000, .divider = {2, 4, 5, 6} },
--
2.45.1
next prev parent reply other threads:[~2024-06-03 1:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 1:26 Benjamin Schneider
2024-06-03 1:26 ` Benjamin Schneider [this message]
2024-06-03 12:46 ` Andrew Lunn
2024-06-03 19:33 ` Ben Schneider
2024-06-05 19:44 ` Pali Rohár
2024-06-05 23:44 ` Andrew Lunn
2024-07-11 16:59 ` Ben Schneider
2024-07-16 8:51 ` Gregory CLEMENT
2024-09-09 13:00 ` Ben Schneider
2024-10-13 3:01 ` Ben Schneider
2024-11-25 21:14 bschnei
2024-12-12 7:07 ` Viresh Kumar
2024-12-15 21:23 ` Marek Behún
2025-01-12 22:49 ` Ben Schneider
2025-02-03 10:57 ` Viresh Kumar
2025-02-19 5:52 ` Viresh Kumar
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=20240603012804.122215-2-ben@bens.haus \
--to=bschnei@gmail.com \
--cc=andrew@lunn.ch \
--cc=ben@bens.haus \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.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
all inboxes | Powered by JetHome®