From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Marc Zyngier <maz@kernel.org>, jens.glathe@oldschoolsolutions.biz
Cc: 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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Steev Klimaszewski <threeway@gmail.com>,
Icecream95 <ixn@disroot.org>
Subject: Re: [PATCH RFC] arm64: dts: qcom: hamoa: Drop cluster_cl5 idle state from CPU clusters
Date: Mon, 8 Jun 2026 13:40:02 +0200 [thread overview]
Message-ID: <2fff4ddf-ea2e-48da-8a7e-e58075597b00@oss.qualcomm.com> (raw)
In-Reply-To: <87bjdp9znw.wl-maz@kernel.org>
On 6/5/26 10:09 AM, Marc Zyngier wrote:
> Hi Jens,
>
> Thanks for sending this.
[...]
> It may be worth adding a comment somewhere in the DTS file, as
> cluster_cl5 is not referenced anymore.
>
> Ideally we'd simply mark cluster-sleep-1 with 'status = "disabled"',
> but I'm not sure Linux (and other OSs that consume this) actively
> parse this property.
>
> Overall, I'd like clarity from the vendor on what can be done to
> better mitigate issues like this. So far, we have been randomly
> disabling features and CPU capabilities each and every time we find
> something broken on these machines, and the list is getting long.
>
> I don't think such course of action is sustainable, and maybe we
> should simply consider marking the full X1 platform as BROKEN so that
> people know what to expect.
Many "Linux-facing" people have been OoO and/or attending various
conferences and an internal sprint for the past 2-3 weeks in a row,
so there weren't a lot of eyes on this.. We're looking into it now.
Konrad
next prev parent reply other threads:[~2026-06-08 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 17:40 [PATCH RFC] arm64: dts: qcom: hamoa: Drop cluster_cl5 idle state from CPU clusters Jens Glathe via B4 Relay
2026-06-04 17:40 ` Jens Glathe
2026-06-05 8:09 ` Marc Zyngier
2026-06-08 11:40 ` Konrad Dybcio [this message]
2026-06-08 12:19 ` Marc Zyngier
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=2fff4ddf-ea2e-48da-8a7e-e58075597b00@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ixn@disroot.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--cc=threeway@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.