From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Taniya Das <taniya.das@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: clock: qcom: Add TCSR_UFS_CLKREF_EN definition
Date: Wed, 9 Sep 2026 09:30:08 +0200 [thread overview]
Message-ID: <20260909-devout-generous-oyster-0efdef@quoll> (raw)
In-Reply-To: <20260905-glymur-ufs-clk-changes-v1-1-cdff2c67a8c2@oss.qualcomm.com>
On Sat, Sep 05, 2026 at 12:20:42AM +0530, Jagadeesh Kona wrote:
> UFS and PCIE_4 share the same clkref enable on Glymur. Hence define
> TCSR_UFS_CLKREF_EN as an alias of TCSR_PCIE_4_CLKREF_EN for UFS consumers
> to reference the shared clkref on Qualcomm Glymur platform.
>
> Signed-off-by: Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>
> ---
> include/dt-bindings/clock/qcom,glymur-tcsr.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/dt-bindings/clock/qcom,glymur-tcsr.h b/include/dt-bindings/clock/qcom,glymur-tcsr.h
> index 72614226b113bb60f1e430fc18e13c46c8b043d3..f338ab4454a14aa75532cd0a6a56b6bbb02f9448 100644
> --- a/include/dt-bindings/clock/qcom,glymur-tcsr.h
> +++ b/include/dt-bindings/clock/qcom,glymur-tcsr.h
> @@ -20,5 +20,6 @@
> #define TCSR_USB3_1_CLKREF_EN 10
> #define TCSR_USB4_1_CLKREF_EN 11
> #define TCSR_USB4_2_CLKREF_EN 12
> +#define TCSR_UFS_CLKREF_EN TCSR_PCIE_4_CLKREF_EN
I could not find usage of this new ABI in your patches. Can you point me?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-09 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 18:50 [PATCH 0/4] clk: qcom: glymur: Add rpmh LNBB clks support and update UFS clk ops Jagadeesh Kona
2026-09-04 18:50 ` [PATCH 1/4] dt-bindings: clock: qcom: Add TCSR_UFS_CLKREF_EN definition Jagadeesh Kona
2026-09-07 7:58 ` Konrad Dybcio
2026-09-09 7:30 ` Krzysztof Kozlowski [this message]
2026-09-11 15:11 ` Jagadeesh Kona
2026-09-04 18:50 ` [PATCH 2/4] clk: qcom: rpmhcc: Add LNBB clocks support for Glymur Jagadeesh Kona
2026-09-05 5:52 ` Abel Vesa
2026-09-04 18:50 ` [PATCH 3/4] clk: qcom: gcc-glymur: Use clk_regmap_phy_mux_ops for GCC UFS muxes Jagadeesh Kona
2026-09-05 5:49 ` Abel Vesa
2026-09-07 7:59 ` Konrad Dybcio
2026-09-04 18:50 ` [PATCH 4/4] clk: qcom: gcc-glymur: use shared ops for GCC UFS RCGs Jagadeesh Kona
2026-09-04 19:02 ` sashiko-bot
2026-09-05 5:45 ` Abel Vesa
2026-09-07 8:02 ` 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=20260909-devout-generous-oyster-0efdef@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=jbrunet+clk@baylibre.com \
--cc=konrad.dybcio@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.