From: sashiko-bot@kernel.org
To: "Loic Poulain" <loic.poulain@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
lee@kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v7 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635
Date: Fri, 24 Jul 2026 07:54:22 +0000 [thread overview]
Message-ID: <20260724075423.601261F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260724-monza-leds-v7-1-0125a3bfea98@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete node name regex update in conditional schema blocks.
--
--- Patch [1]: [PATCH v7 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635 ---
commit 0690191fc4f385657c026eb25eb9afc4e79fffd4
Author: Loic Poulain <loic.poulain@oss.qualcomm.com>
dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635
This commit updates the pca963x binding to support 16 LED channels on the
pca9635. It gives pca9634 its own conditional block and sets the maximum
registry value to 15 unconditionally in the top-level node.
> diff --git a/Documentation/devicetree/bindings/leds/nxp,pca963x.yaml b/Documentation/devicetree/bindings/leds/nxp,pca963x.yaml
> index 938d0e48fe51b..4fda602912f7a 100644
> --- a/Documentation/devicetree/bindings/leds/nxp,pca963x.yaml
> +++ b/Documentation/devicetree/bindings/leds/nxp,pca963x.yaml
> @@ -62,14 +62,14 @@ properties:
> open-drain, newer chips to totem pole).
>
> patternProperties:
> - "^led@[0-9a-f]+$":
> + "^led@[0-9a-f]$":
[ ... ]
> @@ -88,7 +88,13 @@ allOf:
> properties:
> reg:
> maximum: 3
> - else:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - nxp,pca9634
> + then:
> patternProperties:
> "^led@[0-9a-f]+$":
^^^^^^^^^^^^^^^^^^
[Severity: Medium]
The commit message states the node name regex was tightened from
^led@[0-9a-f]+$ to ^led@[0-9a-f]$, but it seems this was only applied to the
top-level patternProperties.
Does this conditional block in Documentation/devicetree/bindings/leds/nxp,pca963x.yaml
also need to be updated to match the top-level regex?
Leaving it as ^led@[0-9a-f]+$ creates a mismatch, and there may be other
allOf conditional blocks (like the one for pca9632/pca9633) that were also
missed.
> properties:
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260724-monza-leds-v7-0-0125a3bfea98@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-07-24 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 7:48 [PATCH v7 0/4] leds: pca963x: Add multicolor support and enable Monza RGB LEDs Loic Poulain
2026-07-24 7:48 ` [PATCH v7 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635 Loic Poulain
2026-07-24 7:54 ` sashiko-bot [this message]
2026-07-24 7:48 ` [PATCH v7 2/4] dt-bindings: leds: nxp,pca963x: add multicolor LED support Loic Poulain
2026-07-24 7:56 ` sashiko-bot
2026-07-24 7:48 ` [PATCH v7 3/4] leds: pca963x: add multicolor LED class support Loic Poulain
2026-07-24 8:02 ` sashiko-bot
2026-07-24 7:48 ` [PATCH v7 4/4] arm64: dts: monaco-arduino-monza: microcontroller LEDs Loic Poulain
2026-07-24 7:55 ` 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=20260724075423.601261F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.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