From: sashiko-bot@kernel.org
To: "Hardeep Sharma" <hardeep.sharma@oss.qualcomm.com>
Cc: linux-clk@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 10/15] dt-bindings: clock: qcom: Add Kuno Global Clock Controller
Date: Fri, 21 Aug 2026 16:18:48 +0000 [thread overview]
Message-ID: <20260821161849.046611F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260821-kuno-soc-support-v3-10-196e2b306368@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The YAML binding requires `#power-domain-cells`, but no power domain macros (GDSCs) are defined in the header file, and the driver provides no implementation.
--
--- Patch [10]: [PATCH v3 10/15] dt-bindings: clock: qcom: Add Kuno Global Clock Controller ---
commit e8474d42563c99c569b8bb564eb4620691ab9a28
Author: Hardeep Sharma <hardeep.sharma@oss.qualcomm.com>
dt-bindings: clock: qcom: Add Kuno Global Clock Controller
Document the Global Clock Controller (GCC) binding and associated
clock/reset IDs for the Qualcomm Kuno SoC.
> diff --git a/Documentation/devicetree/bindings/clock/qcom,kuno-gcc.yaml b/Documentation/devicetree/bindings/clock/qcom,kuno-gcc.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/qcom,kuno-gcc.yaml
[ ... ]
> +required:
> + - compatible
> + - clocks
> + - '#power-domain-cells'
[Severity: Medium]
Does this binding intend to enforce power domains for the Kuno GCC?
The YAML binding requires '#power-domain-cells' here, but looking at the
associated qcom,kuno-gcc.h header file, there are no power domain macros
(GDSCs) defined.
If the hardware does provide power domains, it seems the definitions are
missing from the header. If it does not, this requirement will force device
tree nodes to include meaningless boilerplate to pass validation.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260821-kuno-soc-support-v3-0-196e2b306368@oss.qualcomm.com?part=10
next prev parent reply other threads:[~2026-08-21 16:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 16:08 [PATCH v3 00/15] Add initial support for Qualcomm Kuno SoC Hardeep Sharma
2026-08-21 16:08 ` [PATCH v3 01/15] soc: qcom: geni-se: allow selection on 32-bit ARM Qualcomm SoCs Hardeep Sharma
2026-08-24 7:59 ` Abel Vesa
2026-08-21 16:08 ` [PATCH v3 02/15] dt-bindings: power: rpmpd: Document Kuno RPMh power domains Hardeep Sharma
2026-08-21 16:08 ` [PATCH v3 03/15] pmdomain: qcom: rpmhpd: Add power domains for Kuno Hardeep Sharma
2026-08-24 7:58 ` Abel Vesa
2026-08-21 16:08 ` [PATCH v3 04/15] dt-bindings: clock: qcom,rpmhcc: Add Kuno RPMh clock controller Hardeep Sharma
2026-08-21 16:08 ` [PATCH v3 05/15] clk: qcom: clk-rpmh: Add support for Kuno RPMh clocks Hardeep Sharma
2026-08-21 16:21 ` sashiko-bot
2026-08-24 7:46 ` Abel Vesa
2026-08-21 16:08 ` [PATCH v3 06/15] dt-bindings: interconnect: Add Qualcomm Kuno NoC Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 07/15] interconnect: qcom: Add Kuno interconnect provider driver Hardeep Sharma
2026-08-24 7:57 ` Abel Vesa
2026-08-21 16:09 ` [PATCH v3 08/15] dt-bindings: pinctrl: qcom: Add Kuno TLMM Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 09/15] pinctrl: qcom: Add Kuno pinctrl driver Hardeep Sharma
2026-08-24 7:50 ` Abel Vesa
2026-08-21 16:09 ` [PATCH v3 10/15] dt-bindings: clock: qcom: Add Kuno Global Clock Controller Hardeep Sharma
2026-08-21 16:18 ` sashiko-bot [this message]
2026-08-21 16:09 ` [PATCH v3 11/15] clk: qcom: Add Global Clock Controller driver for Kuno Hardeep Sharma
2026-08-21 16:25 ` sashiko-bot
2026-08-24 7:40 ` Abel Vesa
2026-08-21 16:09 ` [PATCH v3 12/15] dt-bindings: interrupt-controller: qcom,pdc: Add Kuno compatible string Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 13/15] dt-bindings: firmware: qcom,scm: Document SCM on Kuno SoC Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 14/15] dt-bindings: arm: qcom: Document Kuno IDP board Hardeep Sharma
2026-08-21 16:09 ` [PATCH v3 15/15] ARM: dts: qcom: Add initial device tree for Kuno SoC Hardeep Sharma
2026-08-21 16:23 ` sashiko-bot
2026-08-24 7:45 ` Abel Vesa
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=20260821161849.046611F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hardeep.sharma@oss.qualcomm.com \
--cc=linux-clk@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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