From: Christian Loehle <christian.loehle@arm.com>
To: Nick Chan <towinchenmi@gmail.com>,
Hector Martin <marcan@marcan.st>, Sven Peter <sven@svenpeter.dev>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Asahi Linux <asahi@lists.linux.dev>,
Linux ARM Kernel Architecture
<linux-arm-kernel@lists.infradead.org>,
Linux power management <linux-pm@vger.kernel.org>,
Devicetree <devicetree@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 6/7] cpufreq: apple-soc: Set fallback transition latency to APPLE_DVFS_TRANSITION_TIMEOUT
Date: Thu, 12 Dec 2024 11:08:57 +0000 [thread overview]
Message-ID: <2d262f80-81cf-4957-8d4d-ccb5f45e5d75@arm.com> (raw)
In-Reply-To: <df140f26-496d-44ce-8363-ffc908f2effa@arm.com>
On 12/12/24 11:06, Christian Loehle wrote:
> On 12/12/24 07:03, Nick Chan wrote:
>> The driver already assumes transitions will not take longer than
>> APPLE_DVFS_TRANSITION_TIMEOUT in apple_soc_cpufreq_set_target(), so it
>> makes little sense to set CPUFREQ_ETERNAL as the transition latency
>> when the transistion latency is not given by the opp-table.
>>
>> Signed-off-by: Nick Chan <towinchenmi@gmail.com>
>
> Reviewed-by: Christian Loehle <christian.loehle@arm.com>
>
>> ---
>> drivers/cpufreq/apple-soc-cpufreq.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/cpufreq/apple-soc-cpufreq.c b/drivers/cpufreq/apple-soc-cpufreq.c
>> index 94e57f055a5f..c9f31a3653e2 100644
>> --- a/drivers/cpufreq/apple-soc-cpufreq.c
>> +++ b/drivers/cpufreq/apple-soc-cpufreq.c
>> @@ -291,7 +291,7 @@ static int apple_soc_cpufreq_init(struct cpufreq_policy *policy)
>>
>> transition_latency = dev_pm_opp_get_max_transition_latency(cpu_dev);
>> if (!transition_latency)
>> - transition_latency = CPUFREQ_ETERNAL;
>> + transition_latency = APPLE_DVFS_TRANSITION_TIMEOUT * 1000;
s/1000/NSEC_PER_USEC would have been the cleaner choice in case you respin.
>>
>> policy->cpuinfo.transition_latency = transition_latency;
>> policy->dvfs_possible_from_any_cpu = true;
>
>
next prev parent reply other threads:[~2024-12-12 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 7:02 [PATCH v2 0/7] Apple A7-A11, T2 SoC cpufreq support Nick Chan
2024-12-12 7:03 ` [PATCH v2 1/7] dt-bindings: cpufreq: apple,cluster-cpufreq: Add A7-A11, T2 compatibles Nick Chan
2024-12-12 8:25 ` Krzysztof Kozlowski
2024-12-12 7:03 ` [PATCH v2 2/7] cpufreq: apple-soc: Drop setting the PS2 field on M2+ Nick Chan
2024-12-12 7:03 ` [PATCH v2 3/7] cpufreq: apple-soc: Allow per-SoC configuration of APPLE_DVFS_CMD_PS1 Nick Chan
2024-12-12 7:03 ` [PATCH v2 4/7] cpufreq: apple-soc: Use 32-bit read for status register Nick Chan
2024-12-12 7:03 ` [PATCH v2 5/7] cpufreq: apple-soc: Increase cluster switch timeout to 400us Nick Chan
2024-12-12 7:03 ` [PATCH v2 6/7] cpufreq: apple-soc: Set fallback transition latency to APPLE_DVFS_TRANSITION_TIMEOUT Nick Chan
2024-12-12 11:06 ` Christian Loehle
2024-12-12 11:08 ` Christian Loehle [this message]
2024-12-12 7:03 ` [PATCH v2 7/7] cpufreq: apple-soc: Add Apple A7-A8X SoC cpufreq support Nick Chan
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=2d262f80-81cf-4957-8d4d-ccb5f45e5d75@arm.com \
--to=christian.loehle@arm.com \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sven@svenpeter.dev \
--cc=towinchenmi@gmail.com \
--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