From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: eliza: Add CX power domain to GCC
Date: Tue, 24 Mar 2026 16:14:34 +0100 [thread overview]
Message-ID: <87749d7b-b46f-400c-bc0d-932b15c7a75f@oss.qualcomm.com> (raw)
In-Reply-To: <qfaaehigddfg2mawxrat5fp25zu4ioo7ebc4pnojsrzwwx3kk2@4ke3phfbmk62>
On 3/24/26 2:45 PM, Abel Vesa wrote:
> On 26-03-23 21:15:12, Bjorn Andersson wrote:
>> On Sun, Mar 22, 2026 at 06:08:20PM +0200, Abel Vesa wrote:
>>> Recent discussions off-list highlighted that the GCC should vote for the
>>> RPMh CX power domain on Qualcomm platforms.
>>
>> Your commit message should describe the problem that the patch is trying
>> to solve, not the story about how the patch came to be.
>
> Sure. Will fix.
>
>>
>>> Without this, RPMh may not aggregate the correct load for the CX rail,
>>
>> "may not"?
>>
>> In what case will it aggregate the client votes cast on the GDSCs
>> aggregate to anything without the power-domains property?
>
> So my understanding was that RPMh firmware aggregates votes
> internally as it knows the actual parent-child relationship and we were
> supposed to replicate that exactly in kernel for reliability purposes.
>
> Meaning, in theory it should know to aggregate proper load for the CX
> based on GDSCs voting, it's just that it isn't always a sure thing.
>
> Maybe I missunderstood it though.
GDSCs are fancy on/off switches
RPMH votes must be carried out manually and in the kernel that's via
RPMHPD/RPMHCC/ICC
Konrad
next prev parent reply other threads:[~2026-03-24 15:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 16:08 [PATCH 0/3] arm64: dts: qcom: eliza: Left-over review fixes Abel Vesa
2026-03-22 16:08 ` [PATCH 1/3] arm64: dts: qcom: eliza: Coding style clean-ups Abel Vesa
2026-03-22 17:47 ` Dmitry Baryshkov
2026-03-23 10:50 ` Konrad Dybcio
2026-03-22 16:08 ` [PATCH 2/3] arm64: dts: qcom: eliza: Add CX power domain to GCC Abel Vesa
2026-03-22 17:51 ` Dmitry Baryshkov
2026-03-23 10:50 ` Konrad Dybcio
2026-03-23 11:20 ` Abel Vesa
2026-03-22 18:39 ` Dmitry Baryshkov
2026-03-23 10:50 ` Konrad Dybcio
2026-03-24 2:15 ` Bjorn Andersson
2026-03-24 13:45 ` Abel Vesa
2026-03-24 15:14 ` Konrad Dybcio [this message]
2026-03-24 16:17 ` Abel Vesa
2026-03-22 16:08 ` [PATCH 3/3] arm64: dts: qcom: eliza: Disable UFS MCQ mode Abel Vesa
2026-03-22 19:43 ` Krzysztof Kozlowski
2026-03-23 18:30 ` Abel Vesa
2026-03-23 10:51 ` Konrad Dybcio
2026-03-23 18:03 ` Abel Vesa
2026-03-23 18:16 ` Nitin Rawat
2026-03-23 18:28 ` Abel Vesa
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=87749d7b-b46f-400c-bc0d-932b15c7a75f@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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=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