Linux clock framework development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
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 v3 1/4] dt-bindings: clock: qcom: Add QREF regulator supplies for glymur
Date: Sun, 17 May 2026 10:27:39 +0200	[thread overview]
Message-ID: <408f587b-76c2-4fdd-bbe1-89414270b4ee@kernel.org> (raw)
In-Reply-To: <aglUmonGmr2goyOI@hu-qianyu-lv.qualcomm.com>

On 17/05/2026 07:39, Qiang Yu wrote:
> On Thu, May 14, 2026 at 12:22:17PM +0200, Krzysztof Kozlowski wrote:
>> On Wed, May 06, 2026 at 01:43:51AM -0700, Qiang Yu wrote:
>>> Add regulator supply properties for the Glymur TCSR QREF/REFGEN blocks
>>> required by clkref clocks.
>>>
>>> The vdda-qreftx*, vdda-qrefrpt*, and vdda-qrefrx* supplies map to common
>>> QREF TX/RPT/RX components, while SoC-specific topology and instance count
>>> differ. Document them here for qcom,glymur-tcsr.
>>>
>>> Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
>>> ---
>>>  .../bindings/clock/qcom,sm8550-tcsr.yaml           | 57 ++++++++++++++++++++++
>>>  1 file changed, 57 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8550-tcsr.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8550-tcsr.yaml
>>> index 1ccdf4b0f5dd..57921cb63230 100644
>>> --- a/Documentation/devicetree/bindings/clock/qcom,sm8550-tcsr.yaml
>>> +++ b/Documentation/devicetree/bindings/clock/qcom,sm8550-tcsr.yaml
>>> @@ -51,6 +51,63 @@ properties:
>>>    '#reset-cells':
>>>      const: 1
>>>  
>>> +  vdda-refgen-0p9-supply: true
>>> +  vdda-refgen-1p2-supply: true
>>> +  vdda-qrefrx0-0p9-supply: true
>>> +  vdda-qrefrx1-0p9-supply: true
>>> +  vdda-qrefrx2-0p9-supply: true
>>> +  vdda-qrefrx4-0p9-supply: true
>>> +  vdda-qrefrx5-0p9-supply: true
>>> +  vdda-qreftx0-0p9-supply: true
>>> +  vdda-qreftx0-1p2-supply: true
>>> +  vdda-qreftx1-0p9-supply: true
>>> +  vdda-qrefrpt0-0p9-supply: true
>>> +  vdda-qrefrpt1-0p9-supply: true
>>> +  vdda-qrefrpt2-0p9-supply: true
>>> +  vdda-qrefrpt3-0p9-supply: true
>>> +  vdda-qrefrpt4-0p9-supply: true
>>
>> Either I do not understand your previous explanation:
>> CXO -> TX0 -> RPT0 -> RPT1 -> RPT2 -> RX2 -> PCIe4_PHY
>>
>> or this is still wrong. There is no TCSR here, so this proves nothing.
>> If TCSR is TX0, then you do not have five of them...
>>
>> My previous comment stay - you are not describing the actual hardware
>> here.
>>
> The CXO network "-> TX0 -> RPT0 -> RPT1 -> RPT2 -> RX2 ->" is referred to
> as the QREF block, and each component is controlled by the tcsr_clkref_en
> registers.

Still no clue what this -> relation is. Again, describe the hardware.

> 
> If a PHY receives its reference clock from QREF, it will have a clkref_en
> register. However, this register may be located in different regions
> depending on the target. On glymur it resides in TCSR, so I added these
> LDOs QREF required in tcsr yaml.
Registers are not described as supplies.

Best regards,
Krzysztof

  reply	other threads:[~2026-05-17  8:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  8:43 [PATCH v3 0/4] clk: qcom: Add common clkref support and migrate Glymur Qiang Yu
2026-05-06  8:43 ` [PATCH v3 1/4] dt-bindings: clock: qcom: Add QREF regulator supplies for glymur Qiang Yu
2026-05-14 10:22   ` Krzysztof Kozlowski
2026-05-14 10:35     ` Krzysztof Kozlowski
2026-05-17  5:58       ` Qiang Yu
2026-05-17  8:28         ` Krzysztof Kozlowski
2026-05-18  3:35           ` Qiang Yu
2026-05-18  6:59             ` Krzysztof Kozlowski
2026-05-18  7:12               ` Qiang Yu
2026-05-17  5:39     ` Qiang Yu
2026-05-17  8:27       ` Krzysztof Kozlowski [this message]
2026-05-18  3:50         ` Qiang Yu
2026-05-18  7:00           ` Krzysztof Kozlowski
2026-05-18  7:26             ` Qiang Yu
2026-05-19 11:25               ` Manivannan Sadhasivam
2026-05-24 18:38                 ` Krzysztof Kozlowski
2026-05-06  8:43 ` [PATCH v3 2/4] clk: qcom: Add generic clkref_en support Qiang Yu
2026-05-06  8:43 ` [PATCH v3 3/4] clk: qcom: tcsrcc-glymur: Migrate tcsr_pcie_N_clkref_en to clk_ref common helper Qiang Yu
2026-05-06  8:43 ` [PATCH v3 4/4] arm64: dts: qcom: glymur: Add QREF regulator supplies to TCSR 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=408f587b-76c2-4fdd-bbe1-89414270b4ee@kernel.org \
    --to=krzk@kernel.org \
    --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