Re: [PATCH v8 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635
[email protected] Mon, 27 Jul 2026 15:01:06 +0000
| Newsgroups | org.kernel.vger.linux-leds,org.kernel.vger.linux-devicetree |
|---|---|
| Message-ID | <[email protected]> |
Thank you for your contribution! Sashiko AI review found 2 potential issue(= s) to consider: - [Low] The `patternProperties` regex key in `allOf` conditionals does not = match the top-level schema, causing a meta-schema validation (`dt_binding_c= heck`) error. - [Low] The commit message description is not capitalized, violating the LE= D subsystem guidelines. -- --- Patch [1]: [PATCH v8 1/4] dt-bindings: leds: nxp,pca963x: fix reg maxim= um for pca9635 --- commit febe95d1e68d24e8ea2c7f7724fbc41453e15f8d Author: Loic Poulain <[email protected]> dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635 This commit updates the PCA963x LED bindings to support the PCA9635, which has 16 channels. It modifies the top-level node regex and adjusts the=20 conditional blocks to set the appropriate reg maximum for the PCA9634. > dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635 [Severity: Low] This isn't a bug, but the LED subsystem guidelines require capitalizing the= =20 description after the subsystem prefix. Should this be "Fix reg maximum..."? > diff --git a/Documentation/devicetree/bindings/leds/nxp,pca963x.yaml b/Do= cumentation/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). > =20 > patternProperties: > - "^led@[0-9a-f]+$": > + "^led@[0-9a-f]$": > type: object [ ... ] > @@ -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] Does this regex in the conditional block need to be updated to match the new top-level regex "^led@[0-9a-f]$"?=20 In dt-schema, pattern keys inside conditional blocks must exactly match a k= ey=20 defined at the top-level patternProperties, or dt_binding_check will fail.= =20 There is also an earlier conditional block for pca9632/pca9633 that appears= to retain the old "^led@[0-9a-f]+$" regex. Should both of these conditionals b= e=20 updated to prevent meta-schema validation errors? --=20 Sashiko AI review =C2=B7 https://sashiko.dev/#/patchset/20260727-monza-leds= [email protected]?part=3D1