From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sreeshankar K <sreeshankar0910@gmail.com>,
andersson@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: bmasney@redhat.com, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: clock: Add GCC clock bindings for SM7250
Date: Mon, 17 Aug 2026 10:09:02 +0200 [thread overview]
Message-ID: <cc70291b-a945-4a2c-9483-9160cc88e50e@kernel.org> (raw)
In-Reply-To: <20260816090719.892-3-sreeshankar0910@gmail.com>
On 16/08/2026 11:07, Sreeshankar K wrote:
> Add device tree bindings for global clock controller on SM7250 SoC.
>
> Signed-off-by: Sreeshankar K <sreeshankar0910@gmail.com>
Please start using b4. Does this work:
b4 diff '<20260816090719.892-3-sreeshankar0910@gmail.com>'
? No.
> ---
> .../bindings/clock/qcom,gcc-sm7250.yaml | 60 +++++++
> include/dt-bindings/clock/qcom,gcc-sm7250.h | 163 ++++++++++++++++++
> 2 files changed, 223 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sm7250.yaml
> create mode 100644 include/dt-bindings/clock/qcom,gcc-sm7250.h
>
> diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc-sm7250.yaml b/Documentation/devicetree/bindings/clock/qcom,gcc-sm7250.yaml
> new file mode 100644
> index 000000000..822df7dc1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/qcom,gcc-sm7250.yaml
> @@ -0,0 +1,60 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/clock/qcom,gcc-sm7250.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Global Clock & Reset Controller on SM7250
> +
> +maintainers:
> + - Bjorn Andersson <andersson@kernel.org>
> + - Sreeshankar K <sreeshankar0910@gmail.com>
> +
> +description: |
> + Qualcomm global clock control module provides the clocks, resets and power
> + domains on SM7250.
> +
> + See also: include/dt-bindings/clock/qcom,gcc-sm7250.h
> +
> +properties:
> + compatible:
> + const: qcom,gcc-sm7250
> +
> + clocks:
> + items:
> + - description: Board XO source
> + - description: Board active XO source
> + - description: Sleep clock source
Why this cannot go to sm7150 or sm6375 files?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-17 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 9:07 v2 [PATCH 0/2] Add Global Clock Controller (GCC) driver " Sreeshankar K
2026-08-16 9:07 ` [PATCH 1/2] clk: qcom: " Sreeshankar K
2026-08-16 9:07 ` [PATCH 2/2] dt-bindings: clock: Add GCC clock bindings " Sreeshankar K
2026-08-17 8:09 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-16 8:27 [PATCH 0/2] Add Global Clock Controller (GCC) driver " Sreeshankar K
2026-08-16 8:28 ` [PATCH 2/2] dt-bindings: clock: Add GCC clock bindings " Sreeshankar K
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=cc70291b-a945-4a2c-9483-9160cc88e50e@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=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=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=sreeshankar0910@gmail.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
all inboxes | Powered by JetHome®