From: sashiko-bot@kernel.org
To: "Nora Schiffer" <nora.schiffer@ew.tq-group.com>
Cc: linux-leds@vger.kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, lee@kernel.org
Subject: Re: [PATCH 1/7] dt-bindings: leds: pca995x: describe reset-gpios property
Date: Wed, 02 Sep 2026 12:37:59 +0000 [thread overview]
Message-ID: <20260902123759.DC6841F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <6d3600f99c77c31166f0b6a5ccfb7f518b53c4c9.1788350618.git.nora.schiffer@ew.tq-group.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
New issues:
- [Low] The commit message description is not capitalized, violating the LED subsystem guidelines.
Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but the driver validates the child `reg` property against `PCA995X_MAX_OUTPUTS` (24) instead of the chip-specific `num_leds`. This allows 16-channel variants to configure out-of-bounds LEDs.
--
commit ead1262f70ad0044c0eca7c693a6d898fbcc4d44
Author: Nora Schiffer <nora.schiffer@ew.tq-group.com>
dt-bindings: leds: pca995x: describe reset-gpios property
This commit adds the reset-gpios property to the PCA995x device tree binding.
It allows the reset pin of the PCA995x to be described in the Device Tree.
> dt-bindings: leds: pca995x: describe reset-gpios property
[Severity: Low]
This isn't a bug, but does this commit message subject violate the LED
subsystem capitalization rules? The description after the subsystem prefix
should be capitalized.
This is a pre-existing issue, but the driver validates the child reg
property against PCA995X_MAX_OUTPUTS (24) instead of the chip-specific
num_leds:
drivers/leds/leds-pca995x.c:pca995x_probe() {
...
device_for_each_child_node_scoped(dev, child) {
ret = fwnode_property_read_u32(child, "reg", ®);
if (ret)
return ret;
if (reg < 0 || reg >= PCA995X_MAX_OUTPUTS || led_fwnodes[reg])
return -EINVAL;
...
}
[Severity: High]
Does this allow 16-channel variants to configure out-of-bounds LEDs?
Changing the brightness of out-of-bounds LED channels (16-23) on 16-channel
variants (e.g. PCA9955B) calculates a pwmout_addr that overlaps with the
IREF registers (output current control) for channels 0-7.
Could this cause silent hardware state corruption and potential physical
damage to LEDs?
--
Sashiko AI review · https://sashiko.dev/#/patchset/6d3600f99c77c31166f0b6a5ccfb7f518b53c4c9.1788350618.git.nora.schiffer@ew.tq-group.com?part=1
next prev parent reply other threads:[~2026-09-02 12:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 12:22 [PATCH 1/7] dt-bindings: leds: pca995x: describe reset-gpios property Nora Schiffer
2026-09-02 12:22 ` [PATCH 2/7] dt-bindings: leds: pca995x: describe output-gain property Nora Schiffer
2026-09-02 12:31 ` sashiko-bot
2026-09-02 13:10 ` Nora Schiffer
2026-09-03 8:34 ` Lee Jones
2026-09-03 13:09 ` Krzysztof Kozlowski
2026-09-02 12:22 ` [PATCH 3/7] leds: pca995x: add support for reset GPIO Nora Schiffer
2026-09-02 12:41 ` sashiko-bot
2026-09-02 12:22 ` [PATCH 4/7] leds: pca995x: make output gain configurable Nora Schiffer
2026-09-02 12:35 ` sashiko-bot
2026-09-02 12:22 ` [PATCH 5/7] leds: pca995x: add sysfs files for error reporting Nora Schiffer
2026-09-02 12:40 ` sashiko-bot
2026-09-02 12:22 ` [PATCH 6/7] leds: pca995x: do not use full on LED mode Nora Schiffer
2026-09-02 12:39 ` sashiko-bot
2026-09-02 12:22 ` [PATCH 7/7] leds: pca995x: add support for group brightness control Nora Schiffer
2026-09-02 12:43 ` sashiko-bot
2026-09-02 12:37 ` sashiko-bot [this message]
2026-09-02 16:16 ` [PATCH 1/7] dt-bindings: leds: pca995x: describe reset-gpios property Lee Jones
2026-09-03 6:42 ` Nora Schiffer
2026-09-07 7:41 ` Krzysztof Kozlowski
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=20260902123759.DC6841F00A3A@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=nora.schiffer@ew.tq-group.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.