From: Qiang Yu <qiang.yu@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
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 v7 1/7] dt-bindings: clock: qcom: Move glymur TCSR to own binding
Date: Sun, 5 Jul 2026 20:20:58 -0700 [thread overview]
Message-ID: <aksfGiIWxW1RUTfx@hu-qianyu-lv.qualcomm.com> (raw)
In-Reply-To: <6d23a482-4d5c-4444-a533-d89a4602a4dc@kernel.org>
On Fri, Jul 03, 2026 at 04:50:27PM +0200, Krzysztof Kozlowski wrote:
> On 03/07/2026 14:16, Qiang Yu wrote:
> > On Fri, Jul 03, 2026 at 07:58:00AM +0200, Krzysztof Kozlowski wrote:
> >> On Thu, Jul 02, 2026 at 12:36:11AM -0700, Qiang Yu wrote:
> >>> The QREF block supplies reference clocks to PCIe PHYs and requires
> >>> dedicated LDO supplies to operate. The digital control interface for QREF
> >>> (clkref_en registers) resides in TCSR on glymur. Since QREF has no
> >>> dedicated DT node of its own, these supply properties are placed in the
> >>> TCSR node which acts as the control interface for QREF.
> >>>
> >>> Add a dedicated binding file for qcom,glymur-tcsr and document the supply
> >>> properties. As this binding will grow to cover more SoCs, mark the
> >>> required supplies per compatible using an allOf/if/then conditional.
> >>>
> >>> Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
> >>
> >> So you dropped the tag because? Where is the explanation?
> >>
> > Sorry for the confusion. The patch was substantially reworked in v7
> > based on your v6 review comments on patch 2: the compatible was changed
> > from const to an enum, and the allOf/if/then block was moved into this
> > patch upfront. Since the diff changed significantly from what you
> > reviewed, I dropped the tag rather than carry it forward silently.
>
> Dropping tag is fine, but what do the submitting patches say when you
> drop someone's tag?
>
Understood. As per Dcumentation/process/submitting-patches.rst, The
removal should have been explained after the '---' separator of the patch.
- Qiang Yu
next prev parent reply other threads:[~2026-07-06 3:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 7:36 [PATCH v7 0/7] clk: qcom: Add common clkref support and migrate Glymur and Mahua Qiang Yu
2026-07-02 7:36 ` [PATCH v7 1/7] dt-bindings: clock: qcom: Move glymur TCSR to own binding Qiang Yu
2026-07-02 7:46 ` sashiko-bot
2026-07-03 5:58 ` Krzysztof Kozlowski
2026-07-03 12:16 ` Qiang Yu
2026-07-03 14:50 ` Krzysztof Kozlowski
2026-07-06 3:20 ` Qiang Yu [this message]
2026-07-02 7:36 ` [PATCH v7 2/7] dt-bindings: clock: qcom,glymur-tcsr: Add mahua support Qiang Yu
2026-07-02 7:36 ` [PATCH v7 3/7] clk: qcom: Add generic clkref_en support Qiang Yu
2026-07-06 12:24 ` Konrad Dybcio
2026-07-06 13:25 ` Qiang Yu
2026-07-02 7:36 ` [PATCH v7 4/7] clk: qcom: tcsrcc-glymur: Add regulator supplies and migrate to clk_ref helper Qiang Yu
2026-07-02 7:36 ` [PATCH v7 5/7] clk: qcom: tcsrcc-glymur: Add Mahua QREF regulator support Qiang Yu
2026-07-06 12:47 ` Konrad Dybcio
2026-07-06 13:28 ` Qiang Yu
2026-07-02 7:36 ` [PATCH v7 6/7] arm64: dts: qcom: glymur: Add QREF regulator supplies to TCSR Qiang Yu
2026-07-02 7:36 ` [PATCH v7 7/7] arm64: dts: qcom: mahua: " Qiang Yu
2026-07-06 12:50 ` Konrad Dybcio
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=aksfGiIWxW1RUTfx@hu-qianyu-lv.qualcomm.com \
--to=qiang.yu@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=krzk@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=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