mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stefan Riedmüller" <s.riedmueller@phytec.de>
To: Lucas Stach <l.stach@pengutronix.de>,
	rjw@rjwysocki.net, viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	fabio.estevam@nxp.com
Subject: Re: [PATCH] cpufreq: imx6q-cpufreq: Fix speed grading check for imx6qp
Date: Thu, 21 Dec 2017 08:34:39 +0100	[thread overview]
Message-ID: <55b1d40f-1973-ad6a-d01c-1ee063daedcb@phytec.de> (raw)
In-Reply-To: <1513702940.14526.11.camel@pengutronix.de>

Hi,

On 19.12.2017 18:02, Lucas Stach wrote:
> Am Dienstag, den 19.12.2017, 16:56 +0100 schrieb Stefan Riedmueller:
>> Add compatibility for the i.MX 6QuadPlus to make it behave like the
>> i.MX 6Quad, as both SOCs use the same operating points. Otherwise the
>> i.MX 6QuadPlus tries to run with 1.2 GHz even though it only
>> supports 1 GHz.
> There is already an applied patch to fix this issue:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=ccc153a6de1f7741b5ef7c996f9be133772b2092
>
> Regards,
> Lucas
Sorry, I missed that.
So please drop this patch.

Thanks,
Stefan
>> Signed-off-by: Stefan Riedmueller <s.riedmueller@phytec.de>
>> ---
>>   drivers/cpufreq/imx6q-cpufreq.c | 8 +++++---
>>   1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/cpufreq/imx6q-cpufreq.c b/drivers/cpufreq/imx6q-cpufreq.c
>> index 628fe89..5ca1988 100644
>> --- a/drivers/cpufreq/imx6q-cpufreq.c
>> +++ b/drivers/cpufreq/imx6q-cpufreq.c
>> @@ -218,7 +218,7 @@ static void imx6q_opp_check_speed_grading(struct device *dev)
>>>   	 * SPEED_GRADING[1:0] defines the max speed of ARM:
>>>   	 * 2b'11: 1200000000Hz;
>>>   	 * 2b'10: 996000000Hz;
>>> -	 * 2b'01: 852000000Hz; -- i.MX6Q Only, exclusive with 996MHz.
>>> +	 * 2b'01: 852000000Hz; -- i.MX6Q/QP Only, exclusive with 996MHz.
>>>   	 * 2b'00: 792000000Hz;
>>>   	 * We need to set the max speed of ARM according to fuse map.
>>>   	 */
>> @@ -227,13 +227,15 @@ static void imx6q_opp_check_speed_grading(struct device *dev)
>>>   	val &= 0x3;
>>   
>>>   	if ((val != OCOTP_CFG3_SPEED_1P2GHZ) &&
>>> -	     of_machine_is_compatible("fsl,imx6q"))
>>> +	    (of_machine_is_compatible("fsl,imx6q") ||
>>> +	     of_machine_is_compatible("fsl,imx6qp")))
>>>   		if (dev_pm_opp_disable(dev, 1200000000))
>>>   			dev_warn(dev, "failed to disable 1.2GHz OPP\n");
>>>   	if (val < OCOTP_CFG3_SPEED_996MHZ)
>>>   		if (dev_pm_opp_disable(dev, 996000000))
>>>   			dev_warn(dev, "failed to disable 996MHz OPP\n");
>>> -	if (of_machine_is_compatible("fsl,imx6q")) {
>>> +	if (of_machine_is_compatible("fsl,imx6q") ||
>>> +	    of_machine_is_compatible("fsl,imx6qp")) {
>>>   		if (val != OCOTP_CFG3_SPEED_852MHZ)
>>>   			if (dev_pm_opp_disable(dev, 852000000))
>>>   				dev_warn(dev, "failed to disable 852MHz OPP\n");

      reply	other threads:[~2017-12-21  7:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 15:56 Stefan Riedmueller
2017-12-19 17:02 ` Lucas Stach
2017-12-21  7:34   ` Stefan Riedmüller [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=55b1d40f-1973-ad6a-d01c-1ee063daedcb@phytec.de \
    --to=s.riedmueller@phytec.de \
    --cc=fabio.estevam@nxp.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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

all inboxes | Powered by JetHome®