From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Taniya Das <quic_tdas@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8550: Additionally manage MXC power domain in camcc
Date: Thu, 13 Mar 2025 09:25:24 +0000 [thread overview]
Message-ID: <b1be6e61-c620-4df0-810f-036c3c28561d@linaro.org> (raw)
In-Reply-To: <93458252-956b-4630-957b-784cac4ca7ad@linaro.org>
On 13/03/2025 09:10, Bryan O'Donoghue wrote:
> On 13/03/2025 04:39, Taniya Das wrote:
>> power-domains = <&rpmhpd SM8550_MMCX>,
>> <&rpmhpd SM8550_MXC>;
>>
>> Once the above change is incorporated, please add
>>
>> Reviewed-by: Taniya Das<quic_tdas@quicinc.com>
>
> Why does the ordering matter ?
>
> It shouldn't, right ?
Being clear.
I just want to check that you aren't implying a dependency between the
two domains, its just alphanumeric sorting you mean here, right ?
---
bod
next prev parent reply other threads:[~2025-03-13 9:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 22:55 [PATCH 0/2] arm64: dts: qcom: sm8550: camcc: Manage MMCX and MXC Vladimir Zapolskiy
2025-03-03 22:55 ` [PATCH 1/2] dt-bindings: clock: qcom: sm8450-camcc: Allow to specify two power domains Vladimir Zapolskiy
2025-03-03 23:51 ` Dmitry Baryshkov
2025-03-04 0:31 ` Rob Herring (Arm)
2025-03-03 22:55 ` [PATCH 2/2] arm64: dts: qcom: sm8550: Additionally manage MXC power domain in camcc Vladimir Zapolskiy
2025-03-03 23:53 ` Dmitry Baryshkov
2025-03-04 8:30 ` Vladimir Zapolskiy
2025-03-04 8:37 ` Vladimir Zapolskiy
2025-03-04 8:40 ` Dmitry Baryshkov
2025-03-13 4:39 ` Taniya Das
2025-03-13 7:26 ` Dmitry Baryshkov
2025-03-13 7:52 ` Luca Weiss
2025-03-13 11:57 ` Taniya Das
2025-10-17 14:05 ` Luca Weiss
2025-10-20 12:21 ` Konrad Dybcio
2025-10-20 13:00 ` Bryan O'Donoghue
2025-10-21 10:07 ` Luca Weiss
2025-10-21 10:36 ` Luca Weiss
2025-10-21 10:39 ` Konrad Dybcio
2025-10-21 9:48 ` Vladimir Zapolskiy
2025-10-21 9:58 ` Luca Weiss
2025-10-21 11:12 ` Taniya Das
2025-10-21 14:24 ` Luca Weiss
2025-10-21 14:56 ` Luca Weiss
2025-10-22 6:27 ` Taniya Das
2025-03-12 21:00 ` Bryan O'Donoghue
2025-03-13 4:39 ` Taniya Das
2025-03-13 9:10 ` Bryan O'Donoghue
2025-03-13 9:25 ` Bryan O'Donoghue [this message]
2025-03-13 11:32 ` Taniya Das
2025-03-04 1:38 ` [PATCH 0/2] arm64: dts: qcom: sm8550: camcc: Manage MMCX and MXC Rob Herring (Arm)
2025-03-13 11:38 ` Taniya Das
2025-03-26 11:46 ` Jagadeesh Kona
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=b1be6e61-c620-4df0-810f-036c3c28561d@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=vladimir.zapolskiy@linaro.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