Devicetree
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Brian Masney <bmasney@redhat.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Taniya Das <taniya.das@oss.qualcomm.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	krishna.chundru@oss.qualcomm.com
Subject: Re: [PATCH v6 7/8] arm64: dts: qcom: mahua: Add QREF regulator supplies to TCSR
Date: Mon, 29 Jun 2026 14:25:29 +0200	[thread overview]
Message-ID: <103bb3bd-7099-46d0-b0ad-baec1493d742@oss.qualcomm.com> (raw)
In-Reply-To: <akJjrh5z+IVvdRVp@hu-qianyu-lv.qualcomm.com>

On 6/29/26 2:23 PM, Qiang Yu wrote:
> On Mon, Jun 29, 2026 at 12:34:10PM +0200, Konrad Dybcio wrote:
>> On 6/22/26 3:31 PM, Qiang Yu wrote:
>>> On Mon, Jun 22, 2026 at 02:18:54PM +0200, Konrad Dybcio wrote:
>>>> On 6/22/26 7:11 AM, Qiang Yu wrote:
>>>>> Mahua has a different PCIe QREF topology from glymur. Override the TCSR
>>>>> compatible to qcom,mahua-tcsr in mahua.dtsi, and wire up the required
>>>>> LDO supplies for the PCIe clkref paths on the CRD board.
>>>>>
>>>>> Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
>>>>> ---
>>>>>  arch/arm64/boot/dts/qcom/mahua-crd.dts | 15 +++++++++++++++
>>>>>  arch/arm64/boot/dts/qcom/mahua.dtsi    |  4 ++++
>>>>>  2 files changed, 19 insertions(+)
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/qcom/mahua-crd.dts b/arch/arm64/boot/dts/qcom/mahua-crd.dts
>>>>> index 9c8244e892dd..8b42f5174b31 100644
>>>>> --- a/arch/arm64/boot/dts/qcom/mahua-crd.dts
>>>>> +++ b/arch/arm64/boot/dts/qcom/mahua-crd.dts
>>>>> @@ -19,3 +19,18 @@ / {
>>>>>  	model = "Qualcomm Technologies, Inc. Mahua CRD";
>>>>>  	compatible = "qcom,mahua-crd", "qcom,mahua";
>>>>>  };
>>>>> +
>>>>> +&tcsr {
>>>>> +	vdda-qrefrpt0-0p9-supply = <&vreg_l2f_e1_0p83>;
>>>>> +	vdda-qrefrpt1-0p9-supply = <&vreg_l2f_e1_0p83>;
>>>>> +	vdda-qrefrpt2-0p9-supply = <&vreg_l2f_e1_0p83>;
>>>>> +	vdda-qrefrpt3-0p9-supply = <&vreg_l1f_e1_0p82>;
>>>>> +	vdda-qrefrpt4-0p9-supply = <&vreg_l2h_e0_0p72>;
>>>>> +	vdda-qrefrpt5-0p9-supply = <&vreg_l2h_e0_0p72>;
>>>>> +	vdda-qrefrx1-0p9-supply = <&vreg_l2f_e1_0p83>;
>>>>> +	vdda-qrefrx2-0p9-supply = <&vreg_l2f_e1_0p83>;
>>>>> +	vdda-qrefrx3-0p9-supply = <&vreg_l2h_e0_0p72>;
>>>>> +	vdda-qreftx1-0p9-supply = <&vreg_l1f_e1_0p82>;
>>>>> +	vdda-refgen3-0p9-supply = <&vreg_l1f_e1_0p82>;
>>>>> +	vdda-refgen3-1p2-supply = <&vreg_l4f_e1_1p08>;
>>>>
>>>> The supplies are correct, but QREF uses refgen4 on Mahua
>>>>
>>>
>>> The instance is REFGEN4, but its regulator name is refgen3_xxx. Do you
>>> think rename the supplies as vdda-refgen4-0p9-supply is better?
>>
>> Ah, I overlooked this. Maybe 4 could be better here, since the supplies
>> that end up being assigned there match what we call refgen4 on Glymur.
>>
>> But there's no good answer, both options are terrible. Let's add a
>> comment somewhere (in bindings?) describing this mess, perhaps like:
>>
>> # On Mahua, the REFGEN4 block is supplied through pads named REFGEN3
> 
> Okay, it's better to metion this in commit msg.

Doing so in both is good too!

Konrad

  reply	other threads:[~2026-06-29 12:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22  5:11 [PATCH v6 0/8] clk: qcom: Add common clkref support and migrate Glymur and Mahua Qiang Yu
2026-06-22  5:11 ` [PATCH v6 1/8] dt-bindings: clock: qcom: Move glymur TCSR to own binding Qiang Yu
2026-06-22  5:18   ` sashiko-bot
2026-06-22  7:30     ` Krzysztof Kozlowski
2026-06-22  7:29   ` Krzysztof Kozlowski
2026-06-22  5:11 ` [PATCH v6 2/8] dt-bindings: clock: qcom,glymur-tcsr: Add mahua support Qiang Yu
2026-06-22  5:16   ` sashiko-bot
2026-06-22  7:32   ` Krzysztof Kozlowski
2026-06-22  9:51     ` Qiang Yu
2026-06-22  5:11 ` [PATCH v6 3/8] clk: qcom: Add generic clkref_en support Qiang Yu
2026-06-22  5:24   ` sashiko-bot
2026-06-22 12:13   ` Konrad Dybcio
2026-06-22 12:36     ` Qiang Yu
2026-06-22  5:11 ` [PATCH v6 4/8] clk: qcom: tcsrcc-glymur: Add regulator supplies and migrate to clk_ref helper Qiang Yu
2026-06-22  5:11 ` [PATCH v6 5/8] clk: qcom: tcsrcc-glymur: Add Mahua QREF regulator support Qiang Yu
2026-06-22  5:21   ` sashiko-bot
2026-06-22 11:35   ` Konrad Dybcio
2026-06-22 12:49     ` Qiang Yu
2026-06-22 13:03       ` Konrad Dybcio
2026-06-26  3:53         ` Qiang Yu
2026-06-29 10:30           ` Konrad Dybcio
2026-06-29 13:32             ` Qiang Yu
2026-06-29 13:47               ` Konrad Dybcio
2026-06-22  5:11 ` [PATCH v6 6/8] arm64: dts: qcom: glymur: Add QREF regulator supplies to TCSR Qiang Yu
2026-06-22  5:21   ` sashiko-bot
2026-06-22 12:16   ` Konrad Dybcio
2026-06-22 13:24     ` Qiang Yu
2026-06-29 10:38       ` Konrad Dybcio
2026-06-22  5:11 ` [PATCH v6 7/8] arm64: dts: qcom: mahua: " Qiang Yu
2026-06-22  5:22   ` sashiko-bot
2026-06-22 12:18   ` Konrad Dybcio
2026-06-22 13:31     ` Qiang Yu
2026-06-29 10:34       ` Konrad Dybcio
2026-06-29 12:23         ` Qiang Yu
2026-06-29 12:25           ` Konrad Dybcio [this message]
2026-06-22  5:11 ` [PATCH v6 8/8] arm64: dts: qcom: mahua: Switch pcie5_phy ref clock to RPMH_CXO_CLK Qiang Yu
2026-06-22 11:37   ` Konrad Dybcio
2026-06-22 13:34     ` Qiang Yu

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=103bb3bd-7099-46d0-b0ad-baec1493d742@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bmasney@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krishna.chundru@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=qiang.yu@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=taniya.das@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox