From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Fabio Estevam <festevam@denx.de>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Sébastien Szymanski" <sebastien.szymanski@armadeus.com>,
"Stefan Agner" <stefan@agner.ch>,
"Shawn Guo" <shawnguo@kernel.org>, "Marek Vasut" <marex@denx.de>,
"NXP Linux Team" <linux-imx@nxp.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] cpufreq: imx6q: Only disabling 792MHz OPP for i.MX6ULL types below 792MHz
Date: Wed, 8 Nov 2023 10:04:03 +0000 [thread overview]
Message-ID: <5aa0882abf84401a869ad37f7ee8c889@dh-electronics.com> (raw)
In-Reply-To: <188c5e1cddc05f9bd44510e0a4f988df@denx.de>
From: Fabio Estevam
Sent: Tuesday, November 7, 2023 6:48 PM
>
> Hi Christoph,
>
> Thanks for your patch.
>
> On 07/11/2023 13:31, Christoph Niedermaier wrote:
>> For a 900MHz i.MX6ULL CPU the 792MHz OPP is disabled. There is no
>> convincing reason to disable this OPP. If a CPU can run at 900MHz,
>> it should also be able to cope with 792MHz. Looking at the voltage
>> level of 792MHz in [1] (page 24, table 10. "Operating Ranges") the
>> current defined OPP is above the minimum. So the voltage level
>> shouldn't be a problem. Although in [2] (page 24, table 10.
>> "Operating Ranges") 792MHz isn't mentioned there isn't note that
>> 792MHz OPP isn't allowed. Change it to only disable 792MHz OPP for
>
> I find this part:
>
> "792MHz isn't mentioned there isn't note that 792MHz OPP isn't allowed."
>
> a bit confusing.
>
> Maybe:
>
> "However in [2] (page 24, table 10. "Operating Ranges"), it is not
> mentioned that 792MHz OPP isn't allowed."
You are right, your suggestion expresses it more clearly.
I will change it in V2.
>
>
>> [1] https://www.nxp.com/docs/en/data-sheet/IMX6ULLIEC.pdf
>> [2] https://www.nxp.com/docs/en/data-sheet/IMX6ULLCEC.pdf
>>
>> Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
>> Reviewed-by: Marek Vasut <marex@denx.de>
>
> I think it is worth adding a Fixes tag so that this fix could be
> backported
> to stable kernels.
You mean the following fixes tag when the change was introduced?
Fixes: 0aa9abd4c212 ("cpufreq: imx6q: check speed grades for i.MX6ULL")
But if I'm right, then it goes down to version 4.19 and maybe the
commit 11a3b0ac33d9 ("cpufreq: imx6q: don't warn for disabling a non-existing frequency")
is also needed to easily apply.
Regards
Christoph
prev parent reply other threads:[~2023-11-08 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 16:31 [PATCH] cpufreq: imx6q: Only disabling 792MHz OPP for i.MX6ULL types below 792MHz Christoph Niedermaier
2023-11-07 17:47 ` Fabio Estevam
2023-11-08 10:04 ` Christoph Niedermaier [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=5aa0882abf84401a869ad37f7ee8c889@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=festevam@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marex@denx.de \
--cc=rafael@kernel.org \
--cc=sebastien.szymanski@armadeus.com \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
--cc=viresh.kumar@linaro.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