From: Satya Priya Kakitapalli <quic_skakitap@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>
Cc: Ajit Pandey <quic_ajipan@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
Imran Shaik <quic_imrashai@quicinc.com>,
Taniya Das <quic_tdas@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Satya Priya Kakitapalli <quic_skakitap@quicinc.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: [PATCH v2 0/4] Reference the common qcom,gcc.yaml schema
Date: Thu, 17 Jul 2025 12:08:32 +0530 [thread overview]
Message-ID: <20250717-gcc-ref-fixes-v2-0-a2a571d2be28@quicinc.com> (raw)
For all the possible Qualcomm clock controller bindings
add qcom,gcc.yaml reference to unify the common
parts of the binding.
Signed-off-by: Satya Priya Kakitapalli <quic_skakitap@quicinc.com>
---
Changes in v2:
- Drop the patches which didn't have the power-domain-cells.
- Add Krzysztof's Suggested-by tag to all the patches.
- Drop the Reviewed-by tag given on 1st patch as the series got NAK.
- Link to v1: https://lore.kernel.org/r/20250709-gcc-ref-fixes-v1-0-ceddde06775b@quicinc.com
---
Satya Priya Kakitapalli (4):
dt-bindings: clock: qcom,sm8150-camcc: Reference qcom,gcc.yaml
dt-bindings: clock: qcom,mmcc: Reference qcom,gcc.yaml
dt-bindings: clock: qcom,sm4450-camcc: Reference qcom,gcc.yaml
dt-bindings: clock: qcom,sm4450-dispcc: Reference qcom,gcc.yaml
.../devicetree/bindings/clock/qcom,mmcc.yaml | 24 +++-------------------
.../bindings/clock/qcom,sm4450-camcc.yaml | 20 ++++--------------
.../bindings/clock/qcom,sm4450-dispcc.yaml | 20 ++++--------------
.../bindings/clock/qcom,sm8150-camcc.yaml | 20 ++++--------------
4 files changed, 15 insertions(+), 69 deletions(-)
---
base-commit: 26ffb3d6f02cd0935fb9fa3db897767beee1cb2a
change-id: 20250708-gcc-ref-fixes-3f05521a10b1
Best regards,
--
Satya Priya Kakitapalli <quic_skakitap@quicinc.com>
next reply other threads:[~2025-07-17 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 6:38 Satya Priya Kakitapalli [this message]
2025-07-17 6:38 ` [PATCH v2 1/4] dt-bindings: clock: qcom,sm8150-camcc: Reference qcom,gcc.yaml Satya Priya Kakitapalli
2025-07-17 6:47 ` Krzysztof Kozlowski
2025-07-17 6:38 ` [PATCH v2 2/4] dt-bindings: clock: qcom,mmcc: " Satya Priya Kakitapalli
2025-07-17 6:47 ` Krzysztof Kozlowski
2025-07-17 6:38 ` [PATCH v2 3/4] dt-bindings: clock: qcom,sm4450-camcc: " Satya Priya Kakitapalli
2025-07-17 6:47 ` Krzysztof Kozlowski
2025-07-17 6:38 ` [PATCH v2 4/4] dt-bindings: clock: qcom,sm4450-dispcc: " Satya Priya Kakitapalli
2025-07-17 6:48 ` Krzysztof Kozlowski
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=20250717-gcc-ref-fixes-v2-0-a2a571d2be28@quicinc.com \
--to=quic_skakitap@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jeff.hugo@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=quic_ajipan@quicinc.com \
--cc=quic_imrashai@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).