From: sashiko-bot@kernel.org
To: "Jan Carlo Roleda" <jancarlo.roleda@analog.com>
Cc: lee@kernel.org, linux-leds@vger.kernel.org, robh@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 1/2] dt-bindings: leds: Document LTC3208 Multidisplay LED Driver
Date: Wed, 29 Jul 2026 23:20:21 +0000 [thread overview]
Message-ID: <20260729232022.4A8481F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260730-upstream-ltc3208-v8-1-6bdcc35e65d7@analog.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The schema omits `#address-cells` and `#size-cells` from the top-level `required` list, which allows structurally incomplete device tree nodes to silently pass validation.
--
--- Patch [1]: [PATCH v8 1/2] dt-bindings: leds: Document LTC3208 Multidisplay LED Driver ---
commit 40f57e6c55c9069959e21c4ed832c353a3472f0a
Author: Jan Carlo Roleda <jancarlo.roleda@analog.com>
dt-bindings: leds: Document LTC3208 Multidisplay LED Driver
This commit adds Devicetree Documentation for the LTC3208 Multidisplay LED
Driver.
> diff --git a/Documentation/devicetree/bindings/leds/adi,ltc3208.yaml b/Documentation/devicetree/bindings/leds/adi,ltc3208.yaml
> new file mode 100644
> index 0000000000000..0a01e07e0ab70
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/adi,ltc3208.yaml
[ ... ]
> +patternProperties:
> + "^led@[0-7]$":
> + type: object
> + $ref: /schemas/leds/common.yaml#
> + unevaluatedProperties: false
> + properties:
> + reg:
> + description:
> + LED Channel Number. each channel maps to a specific channel group used
> + to configure the brightness level of the output pins corresponding to
> + the channel.
> + enum:
> + - 0 # Main Channel (8-bit brightness)
> + - 1 # Sub Channel (8-bit brightness)
> + - 2 # AUX Channel (4-bit brightness)
> + - 3 # Camera Channel, Low-side byte (4-bit brightness)
> + - 4 # Camera Channel, High-side byte (4-bit brightness)
> + - 5 # Red Channel (4-bit brightness)
> + - 6 # Blue Channel (4-bit brightness)
> + - 7 # Green Channel (4-bit brightness)
> + required:
> + - reg
> +
> +required:
> + - compatible
> + - reg
[Severity: Low]
Should #address-cells and #size-cells be included in this top-level required
list?
The schema defines child LED nodes in patternProperties that strictly
require a reg property. This means the parent controller node must establish
an address space for them.
If #address-cells and #size-cells are omitted from the required list, a
device tree author could configure the node with led@X child nodes but forget
to set the addressing cells, and the structurally incomplete device tree
nodes could silently pass schema validation.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260730-upstream-ltc3208-v8-0-6bdcc35e65d7@analog.com?part=1
next prev parent reply other threads:[~2026-07-29 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 23:14 [PATCH v8 0/2] Add support for LTC3208 multi-display driver Jan Carlo Roleda
2026-07-29 23:14 ` [PATCH v8 1/2] dt-bindings: leds: Document LTC3208 Multidisplay LED Driver Jan Carlo Roleda
2026-07-29 23:20 ` sashiko-bot [this message]
2026-07-29 23:14 ` [PATCH v8 2/2] leds: ltc3208: Add driver for " Jan Carlo Roleda
2026-07-29 23:22 ` 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=20260729232022.4A8481F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jancarlo.roleda@analog.com \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--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