From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
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>,
Abel Vesa <abelvesa@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm850-lenovo-yoga-c630: lower PSCI cluster idle
Date: Fri, 15 May 2026 13:03:05 +0200 [thread overview]
Message-ID: <e2c54638-2849-40dc-9c68-636c04719814@oss.qualcomm.com> (raw)
In-Reply-To: <d10fa5ef-4d2d-4fa8-938c-6ec74a823bba@oss.qualcomm.com>
On 5/15/26 1:01 PM, Dmitry Baryshkov wrote:
> On 15/05/2026 14:00, Konrad Dybcio wrote:
>> On 4/28/26 9:36 PM, Dmitry Baryshkov wrote:
>>> With the default PSCI suspend value for cluster idle state Lenovo Yoga
>>> C630 isn't stable enough. For example it might reset if display device
>>> isn't probed early enough. Drop one of the bits from the PSCI suspend
>>> value to make C630 work in stable way.
>>>
>>> Fixes: a1ade6cac5a2 ("arm64: dts: qcom: sdm845: Switch PSCI cpu idle states from PC to OSI")
>>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>>> ---
>>> arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts b/arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts
>>> index e41200839dbe..e6c67016552a 100644
>>> --- a/arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts
>>> +++ b/arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts
>>> @@ -347,6 +347,10 @@ &cdsp_pas {
>>> status = "okay";
>>> };
>>> +&cluster_sleep_0 {
>>> + arm,psci-suspend-param = <0x41003244>;
>>> +};
>>
>> Is it better if you do hack in a
>>
>> qmp_send(qmp, "{class: cx_mol, res: cx, val: mol}");
>
> Any clarification? Then I can try hacking it in.
This will send a message to AOSS to intrusct it to prevent CX from
collapsing
You'd need this somewhere early enough so as not to crash
alternatively, the good ol'
diff --git a/drivers/interconnect/qcom/sdm845.c b/drivers/interconnect/qcom/sdm845.c
index 6d5bbeda0689..2fea94618839 100644
--- a/drivers/interconnect/qcom/sdm845.c
+++ b/drivers/interconnect/qcom/sdm845.c
@@ -1786,7 +1786,7 @@ static struct platform_driver qnoc_driver = {
.driver = {
.name = "qnoc-sdm845",
.of_match_table = qnoc_of_match,
- .sync_state = icc_sync_state,
+ //.sync_state = icc_sync_state,
},
};
module_platform_driver(qnoc_driver);
should give you a similar result
Konrad
next prev parent reply other threads:[~2026-05-15 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 19:36 [PATCH] arm64: dts: qcom: sdm850-lenovo-yoga-c630: lower PSCI cluster idle Dmitry Baryshkov
2026-04-28 20:38 ` Abel Vesa
2026-04-28 21:43 ` Dmitry Baryshkov
2026-05-15 11:00 ` Konrad Dybcio
2026-05-15 11:01 ` Dmitry Baryshkov
2026-05-15 11:03 ` Konrad Dybcio [this message]
2026-05-15 11:09 ` Dmitry Baryshkov
2026-05-15 11:13 ` Konrad Dybcio
2026-05-15 11:15 ` Dmitry Baryshkov
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=e2c54638-2849-40dc-9c68-636c04719814@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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