Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Loic Poulain" <loic.poulain@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
	linux-leds@vger.kernel.org, lee@kernel.org
Subject: Re: [PATCH v6 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635
Date: Wed, 15 Jul 2026 13:51:55 +0000	[thread overview]
Message-ID: <20260715135155.E5C311F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715-monza-leds-v6-1-d1724bb7fe3d@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message claims to tighten the node name regex from `[0-9a-f]+` to `[0-9a-f]` to match the single-digit hardware limit. However, this change was only applied to the top-level `patternProperties`. The corresponding regexes inside the `allOf` conditional blocks for older chip generations were neglected and still allow multiple hex digits.
--

--- Patch [1]: [PATCH v6 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635 ---
commit a500d493e0680c38dffc3b668e4fe9888ec4d0bd
Author: Loic Poulain <loic.poulain@oss.qualcomm.com>
Subject: dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635

This commit increases the maximum reg value to 15 in the top-level led node
to support 16 channels on the pca9635. It refactors the allOf conditionals
to give pca9634 its own block and changes the top-level regex constraint to
match a single hexadecimal digit.

> 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

[ ... ]

> @@ -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 regex is tightened to single-digit [0-9a-f],
but is it intentional that the patternProperties inside the allOf blocks for
older generations still use the multiple-digit [0-9a-f]+ pattern?

While the top-level constraint handles the validation correctly, retaining
the '+' in the nested conditional blocks for pca9634 (and the pca9632 and
pca9633 block just above this hunk) leaves the schema internally
inconsistent with the stated intent.

>            properties:
>              reg:

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260715-monza-leds-v6-0-d1724bb7fe3d@oss.qualcomm.com?part=1

  reply	other threads:[~2026-07-15 13:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 13:44 [PATCH v6 0/4] leds: pca963x: Add multicolor support and enable Monza RGB LEDs Loic Poulain
2026-07-15 13:44 ` [PATCH v6 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635 Loic Poulain
2026-07-15 13:51   ` sashiko-bot [this message]
2026-07-15 13:44 ` [PATCH v6 2/4] dt-bindings: leds: nxp,pca963x: add multicolor LED support Loic Poulain
2026-07-15 13:52   ` sashiko-bot
2026-07-15 13:44 ` [PATCH v6 3/4] leds: pca963x: add multicolor LED class support Loic Poulain
2026-07-15 13:57   ` sashiko-bot
2026-07-15 13:44 ` [PATCH v6 4/4] arm64: dts: monaco-arduino-monza: microcontroller LEDs Loic Poulain
2026-07-15 13:54   ` 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=20260715135155.E5C311F000E9@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