From: sashiko-bot@kernel.org
To: "Richard Genoud" <richard.genoud@bootlin.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v7 1/4] dt-bindings: pwm: allwinner: add h616 pwm compatible
Date: Fri, 03 Jul 2026 15:26:30 +0000 [thread overview]
Message-ID: <20260703152631.305511F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260703152215.192859-2-richard.genoud@bootlin.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `#clock-cells` property is missing from the `required` list for the `allwinner,sun50i-h616-pwm` compatible.
--
commit d7a701d864bf3d5f7e7d179d4498b5006b8bf3f7
Author: Richard Genoud <richard.genoud@bootlin.com>
dt-bindings: pwm: allwinner: add h616 pwm compatible
This commit introduces the Allwinner H616 PWM block to the sun4i pwm
binding. It adds the new compatible string and handles the new clock
provider capabilities introduced by the H616 bypass mode.
> diff --git a/Documentation/devicetree/bindings/pwm/allwinner,sun4i-a10-pwm.yaml b/Documentation/devicetree/bindings/pwm/allwinner,sun4i-a10-pwm.yaml
> index 1197858e431f2..4f58110ec98f7 100644
> --- a/Documentation/devicetree/bindings/pwm/allwinner,sun4i-a10-pwm.yaml
> +++ b/Documentation/devicetree/bindings/pwm/allwinner,sun4i-a10-pwm.yaml
[ ... ]
> @@ -83,6 +89,17 @@ allOf:
> clocks:
> maxItems: 1
>
> + - if:
> + not:
> + properties:
> + compatible:
> + contains:
> + const: allwinner,sun50i-h616-pwm
> +
> + then:
> + properties:
> + "#clock-cells": false
> +
[Severity: Medium]
Should #clock-cells be added to the required properties for the H616 variant?
The commit message mentions that the H616 PWM block can output a clock
used as an input for other devices. While the conditional block above
correctly prevents older hardware variants from using #clock-cells, it
appears to leave the property optional for the H616.
If a device tree node for allwinner,sun50i-h616-pwm omits #clock-cells,
it might silently pass schema validation but fail at runtime when dependent
subsystems try to use it as a clock provider.
Would it make sense to add an else clause here (or a separate conditional)
to explicitly require #clock-cells when the H616 compatible is present?
> required:
> - compatible
> - reg
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260703152215.192859-1-richard.genoud@bootlin.com?part=1
next prev parent reply other threads:[~2026-07-03 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 15:22 [PATCH v7 0/4] Introduce Allwinner H616 PWM controller Richard Genoud
2026-07-03 15:22 ` [PATCH v7 1/4] dt-bindings: pwm: allwinner: add h616 pwm compatible Richard Genoud
2026-07-03 15:26 ` sashiko-bot [this message]
2026-07-03 15:22 ` [PATCH v7 2/4] pwm: sun8i: Add H616 PWM support Richard Genoud
2026-07-03 15:33 ` sashiko-bot
2026-07-03 16:00 ` Philipp Zabel
2026-07-03 15:22 ` [PATCH v7 3/4] arm64: dts: allwinner: h616: add PWM controller Richard Genoud
2026-07-03 15:22 ` [PATCH v7 4/4] MAINTAINERS: Add entry on Allwinner sun8i/H616 PWM driver Richard Genoud
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=20260703152631.305511F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=richard.genoud@bootlin.com \
--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