From: "Maulik Shah (mkshah)" <maulik.shah@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Daniel J Blueman <daniel@quora.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: hamoa/x1: fix idle exit latency
Date: Fri, 20 Feb 2026 16:40:08 +0530 [thread overview]
Message-ID: <0f566afc-27ca-4326-a83b-aac92ba50037@oss.qualcomm.com> (raw)
In-Reply-To: <8e670f28-9a2e-4495-9b84-8b1d9c0542ba@oss.qualcomm.com>
On 2/20/2026 3:11 PM, Konrad Dybcio wrote:
> On 2/20/26 8:02 AM, Daniel J Blueman wrote:
>> Designs based on the Qualcomm X1 Hamoa reference platform report:
>> driver: Idle state 1 target residency too low
>>
>> This is because the declared X1 idle entry plus exit latency of 680us
>> exceeds the declared minimum 600us residency time:
>> entry-latency-us = <180>;
>> exit-latency-us = <500>;
>> min-residency-us = <600>;
>>
>> As 500us idle exit latency is overly conservative, fix this to be a more
>> realistic 200us, in range of similar silicon. Tested on a Lenovo Yoga Slim
>> 7x with Qualcomm X1E-80-100.
>>
>> Signed-off-by: Daniel J Blueman <daniel@quora.org>
>> ---
>> arch/arm64/boot/dts/qcom/hamoa.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/hamoa.dtsi b/arch/arm64/boot/dts/qcom/hamoa.dtsi
>> index a17900eacb20..b870f4dc9c42 100644
>> --- a/arch/arm64/boot/dts/qcom/hamoa.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/hamoa.dtsi
>> @@ -269,7 +269,7 @@ cluster_c4: cpu-sleep-0 {
>> idle-state-name = "ret";
>> arm,psci-suspend-param = <0x00000004>;
>> entry-latency-us = <180>;
>> - exit-latency-us = <500>;
>> + exit-latency-us = <200>;
>> min-residency-us = <600>;
>
> +Maulik?
>
> Konrad
Linux dt idle driver sums up entry & exit latency and displays final number as total exit latency at
/sys/devices/system/cpu/cpu*/cpuidle/state1/latency
Can you please keep 320 usec as exit-latency-us to match with downstream 500usec total exit latency number from cluster_c4 state.
Thanks,
Maulik
prev parent reply other threads:[~2026-02-20 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 7:02 Daniel J Blueman
2026-02-20 9:41 ` Konrad Dybcio
2026-02-20 11:10 ` Maulik Shah (mkshah) [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=0f566afc-27ca-4326-a83b-aac92ba50037@oss.qualcomm.com \
--to=maulik.shah@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@quora.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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®