Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Loic Poulain" <loic.poulain@oss.qualcomm.com>
Cc: lee@kernel.org, devicetree@vger.kernel.org, robh@kernel.org,
	conor+dt@kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635
Date: Wed, 08 Jul 2026 14:26:30 +0000	[thread overview]
Message-ID: <20260708142630.B780E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260708-monza-leds-v4-1-a7acfc524c0b@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] Incomplete refactoring of node name regex in `allOf` conditionals, contradicting commit message.
- [Low] Commit message description starts with a lowercase letter, violating LED subsystem naming conventions.
--

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

dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635

This commit updates the pca9635 LED controller bindings to support 16 channels
by separating the pca9634 conditional logic. It also sets a default register
maximum of 15 and restricts the node name regex to a single hex digit.

> dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635

[Severity: Low]
This isn't a bug, but the commit message subject starts with a lowercase
letter. The LED subsystem conventions require capitalizing the description
after the prefix. Could this be updated to "Fix reg maximum for pca9635"?

> 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: Low]
The commit message states the node name regex was tightened to
"^led@[0-9a-f]$", but it appears the broader "^led@[0-9a-f]+$" regex was left
in place in the allOf conditionals.

While the multi-digit hex nodes will still be rejected globally due to the
root schema, should this conditional and the similar conditional for
nxp,pca9632/pca9633 earlier in the file also be updated to match the commit
message?

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

  reply	other threads:[~2026-07-08 14:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 14:18 [PATCH v4 0/4] leds: pca963x: Add multicolor support and enable Monza RGB LEDs Loic Poulain
2026-07-08 14:19 ` [PATCH v4 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635 Loic Poulain
2026-07-08 14:26   ` sashiko-bot [this message]
2026-07-08 16:25   ` Conor Dooley
2026-07-08 14:19 ` [PATCH v4 2/4] dt-bindings: leds: nxp,pca963x: add multicolor LED support Loic Poulain
2026-07-08 14:27   ` sashiko-bot
2026-07-08 16:27   ` Conor Dooley
2026-07-08 14:19 ` [PATCH v4 3/4] leds: pca963x: add multicolor LED class support Loic Poulain
2026-07-08 14:38   ` sashiko-bot
2026-07-08 14:19 ` [PATCH v4 4/4] arm64: dts: monaco-arduino-monza: microcontroller LEDs Loic Poulain
2026-07-08 14:30   ` 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=20260708142630.B780E1F000E9@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