From: "Pali Rohár" <pali@kernel.org>
To: nnet <nnet@fastmail.fm>
Cc: "Marek Behún" <kabel@kernel.org>,
andrew@lunn.ch, luka.perkov@sartura.hr, sboyd@kernel.org,
gregory.clement@bootlin.com, a.heider@gmail.com,
linux-kernel@vger.kernel.org, vladimir.vid@sartura.hr,
mturquette@baylibre.com, rmk+kernel@armlinux.org.uk,
tmn505@gmail.com, gerald@gk2.net, miquel.raynal@bootlin.com,
kostap@marvell.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH mvebu v2 00/10] Armada 37xx: Fix cpufreq changing base CPU speed to 800 MHz from 1000 MHz
Date: Fri, 19 Feb 2021 20:33:02 +0100 [thread overview]
Message-ID: <20210219193302.odcjcaukxxjaedd5@pali> (raw)
In-Reply-To: <d057d7f7-27a5-45ec-88f0-a653572a8ca6@www.fastmail.com>
On Tuesday 16 February 2021 08:27:10 nnet wrote:
> > Therefore I'm thinking if the correct way is instead to use L1 := L0 voltage value for 1/1.2 GHz mode.
>
> This latest 04/10 works fine for me going 600MHz <-> 1.2GHz under with and without load.
Ok, thanks for testing! Just to note that typical documented value for
1.2GHz mode is 1.155V, so it would be useful to know if this value could
be stable for L1 with 1.2GHz mode.
I'm thinking that for 1GHz variant it would be better to rather use
1.108V like in my original patch as this is already tested by lot of
people, nobody complained yet and it can be lower value as L0 (so there
is benefit to decrease CPU frequency when CPU is idle).
For 1.2GHz variant I still do not know. You wrote that 1.132V is
unstable, so it cannot be used for sure. Documented typical value 1.155V
is bigger, so maybe it can be stable but needs testing. And stable seems
to be L0 value... But then I do not see a benefit for downclocking CPU
from 1.2 GHz frequency in L0 to 600 MHz freq. in L1 if it use same CPU
voltage... But it is still better than unstable CPU with crashes!
Could you test if 1.155V voltage for L1 is stable on 1.2 GHz variant?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-19 19:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d59ba191-43db-4b7b-b201-62a60ca752c0@www.fastmail.com>
2021-02-09 21:33 ` [PATCH mvebu v2 00/10] Armada 37xx: Fix cpufreq changing base CPU speed to 800 MHz from 1000 MHz Pali Rohár
2021-02-09 21:45 ` nnet
2021-02-09 22:42 ` Pali Rohár
2021-02-09 22:52 ` nnet
2021-02-09 22:56 ` Pali Rohár
2021-02-09 23:16 ` nnet
2021-02-09 23:26 ` Marek Behún
2021-02-10 1:31 ` nnet
2021-02-10 1:51 ` nnet
2021-02-10 2:07 ` nnet
2021-02-10 9:23 ` Pali Rohár
2021-02-10 17:34 ` nnet
2021-02-10 18:03 ` Pali Rohár
2021-02-10 19:08 ` nnet
2021-02-10 19:18 ` Marek Behún
2021-02-11 19:55 ` Pali Rohár
2021-02-11 20:22 ` nnet
2021-02-11 23:44 ` Pali Rohár
2021-02-12 0:41 ` nnet
2021-02-13 10:01 ` Pali Rohár
2021-02-13 18:30 ` nnet
2021-02-14 12:33 ` Pali Rohár
2021-02-16 5:48 ` nnet
2021-02-16 10:41 ` Pali Rohár
2021-02-16 16:27 ` nnet
2021-02-19 19:33 ` Pali Rohár [this message]
2021-02-22 3:17 ` nnet
2021-02-22 9:51 ` Pali Rohár
2021-02-22 16:36 ` nnet
2021-02-22 16:40 ` Philip Soares
2021-02-10 2:12 ` Marek Behún
2021-01-14 12:40 Pali Rohár
2021-02-01 14:35 ` Tomasz Maciej Nowak
2021-02-03 19:29 ` Anders Trier Olesen
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=20210219193302.odcjcaukxxjaedd5@pali \
--to=pali@kernel.org \
--cc=a.heider@gmail.com \
--cc=andrew@lunn.ch \
--cc=gerald@gk2.net \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=kostap@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=miquel.raynal@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=nnet@fastmail.fm \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sboyd@kernel.org \
--cc=tmn505@gmail.com \
--cc=vladimir.vid@sartura.hr \
/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