Linux clock framework development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Andre Przywara" <andre.przywara@arm.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, linux-sunxi@lists.linux.dev,
	conor+dt@kernel.org
Subject: Re: [PATCH v2 3/5] dt-bindings: clock: sun55i-a523-ccu: Add A523 CPU CCU clock controller
Date: Thu, 17 Sep 2026 22:46:24 +0000	[thread overview]
Message-ID: <20260917224625.76AFF1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917223913.1855301-4-andre.przywara@arm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: clock: sun55i-a523-ccu: CPU CCU incorrectly requires #reset-cells
--

commit 6b88ed1238e42f9cf204f24c2d92453688b20a13
Author: Andre Przywara <andre.przywara@arm.com>

dt-bindings: clock: sun55i-a523-ccu: Add A523 CPU CCU clock controller
    
There are four clock controllers in the A523 SoC, but only three are
described in the DT binding so far.
    
Add a description for the CPU CCU, which provides separate clocks for
the two CPU clusters and the DSU interconnect.

> diff --git a/Documentation/devicetree/bindings/clock/allwinner,sun55i-a523-ccu.yaml b/Documentation/devicetree/bindings/clock/allwinner,sun55i-a523-ccu.yaml
> index 58be701a720ea..98d47d2aabc48 100644
> --- a/Documentation/devicetree/bindings/clock/allwinner,sun55i-a523-ccu.yaml
> +++ b/Documentation/devicetree/bindings/clock/allwinner,sun55i-a523-ccu.yaml
> @@ -19,6 +19,7 @@ properties:
>    compatible:
>      enum:
>        - allwinner,sun55i-a523-ccu
> +      - allwinner,sun55i-a523-cpu-ccu

[Severity: Low]
Does the new sun55i-a523-cpu-ccu compatible string incorrectly inherit the
global #reset-cells requirement?

Looking at the binding, #reset-cells is globally required:

required:
  - "#clock-cells"
  - "#reset-cells"
  - compatible

Since the CPU CCU does not seem to provide resets, will this force device tree
nodes to include an unnecessary #reset-cells property to pass schema
validation?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917223913.1855301-1-andre.przywara@arm.com?part=3

  reply	other threads:[~2026-09-17 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 22:39 [PATCH v2 0/5] arm64: allwinner: a523: Enable CPU clocks Andre Przywara
2026-09-17 22:39 ` [PATCH v2 1/5] clk: sunxi-ng: generalise update bit Andre Przywara
2026-09-21 15:47   ` Chen-Yu Tsai
2026-09-17 22:39 ` [PATCH v2 2/5] clk: sunxi-ng: mp: support clocks with just a shift register Andre Przywara
2026-09-18  3:51   ` Chen-Yu Tsai
2026-09-24  6:54     ` Andre Przywara
2026-09-17 22:39 ` [PATCH v2 3/5] dt-bindings: clock: sun55i-a523-ccu: Add A523 CPU CCU clock controller Andre Przywara
2026-09-17 22:46   ` sashiko-bot [this message]
2026-09-17 22:39 ` [PATCH v2 4/5] clk: sunxi-ng: add support for the A523/T527 CPU CCU Andre Przywara
2026-09-17 22:51   ` sashiko-bot
2026-09-17 22:39 ` [PATCH v2 5/5] arm64: dts: allwinner: a523: add CPU clocks Andre Przywara
2026-09-17 22:46   ` sashiko-bot

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=20260917224625.76AFF1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --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