From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Abel Vesa <abel.vesa@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>
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] arm64: dts: qcom: Introduce Eliza Soc base dtsi
Date: Wed, 18 Mar 2026 12:27:50 +0100 [thread overview]
Message-ID: <aaf6a9f6-ad1f-4e66-891e-85502ed7a076@kernel.org> (raw)
In-Reply-To: <78efa6d6-5204-4146-b95b-9ebc18a546f5@oss.qualcomm.com>
On 18/03/2026 12:10, Konrad Dybcio wrote:
> On 3/18/26 11:45 AM, Krzysztof Kozlowski wrote:
>> On 18/03/2026 11:19, Abel Vesa wrote:
>>> + };
>
> [...]
>
>>> + cpu_pd7: power-domain-cpu7 {
>>> + #power-domain-cells = <0>;
>>> + power-domains = <&cluster_pd>;
>>> + domain-idle-states = <&cluster2_c4>;
>>
>> ...here.
>>
>> Each cluster has different entry/exit latencies, but @Konrad insisted to
>> represent here only one cluster. I believe it is not correct, but I am
>> fine with it, however my question remains: how does this work in such
>> case - which domain idle state is really used?
>>
>> It's more of a question to Konrad since he wanted one cluster...
>
> I *believe* cpuidle functions fine as-is (i.e. each CPU gets assigned the
> correct idle states etc. and the system/"one big cluster" PD is also correct)..
> I am open to being proven wrong
I guess it will work fine.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-18 11:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 10:19 [PATCH v3 0/3] arm64: dts: qcom: Add base support for Eliza SoC and its MTP board Abel Vesa
2026-03-18 10:19 ` [PATCH v3 1/3] dt-bindings: arm: qcom: Document " Abel Vesa
2026-03-18 10:19 ` [PATCH v3 2/3] arm64: dts: qcom: Introduce Eliza Soc base dtsi Abel Vesa
2026-03-18 10:45 ` Krzysztof Kozlowski
2026-03-18 11:10 ` Konrad Dybcio
2026-03-18 11:27 ` Krzysztof Kozlowski [this message]
2026-03-18 11:18 ` Konrad Dybcio
2026-03-18 11:23 ` Krzysztof Kozlowski
2026-03-19 14:29 ` Abel Vesa
2026-03-18 10:19 ` [PATCH v3 3/3] arm64: dts: qcom: eliza: Enable Eliza MTP board support Abel Vesa
2026-03-18 10:31 ` Dmitry Baryshkov
2026-03-18 10:41 ` Krzysztof Kozlowski
2026-03-18 11:30 ` Konrad Dybcio
2026-03-19 2:46 ` [PATCH v3 0/3] arm64: dts: qcom: Add base support for Eliza SoC and its MTP board Bjorn Andersson
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=aaf6a9f6-ad1f-4e66-891e-85502ed7a076@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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