From: sashiko-bot@kernel.org
To: "Ronald Claveau via B4 Relay"
<devnull+linux-kernel-dev.aliel.fr@kernel.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
neil.armstrong@linaro.org, krzk+dt@kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2 3/3] arm64: dts: amlogic: t7: khadas-vim4: add PWM-driven status LED
Date: Thu, 14 May 2026 04:05:19 +0000 [thread overview]
Message-ID: <20260514040520.5FF16C2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260513-add-kvim4-sysled-v2-3-3ec9779e8875@aliel.fr>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The subnode for the LED under `pwm-leds` is named `status`, which violates the `leds-pwm` device tree binding schema.
--
commit fa7913b140af3e7d64c22b109d1765f504180ad0
Author: Ronald Claveau <linux-kernel-dev@aliel.fr>
arm64: dts: amlogic: t7: khadas-vim4: add PWM-driven status LED
This commit enables the pwm_ao_cd controller and adds a pwm-leds node with a
heartbeat trigger to expose the status LED on the VIM4 board.
> diff --git a/arch/arm64/boot/dts/amlogic/amlogic-t7-a311d2-khadas-vim4.dts b/arch/arm64/boot/dts/amlogic/amlogic-t7-a311d2-khadas-vim4.dts
> --- a/arch/arm64/boot/dts/amlogic/amlogic-t7-a311d2-khadas-vim4.dts
> +++ b/arch/arm64/boot/dts/amlogic/amlogic-t7-a311d2-khadas-vim4.dts
> @@ -53,6 +53,16 @@ dc_in: regulator-dc-in {
> regulator-always-on;
> };
>
> + pwm-leds {
> + compatible = "pwm-leds";
> +
> + status {
Does this subnode name trigger a device tree schema validation error?
The leds-pwm binding schema in
Documentation/devicetree/bindings/leds/leds-pwm.yaml specifies
additionalProperties: false and expects child node names to match the
regular expression ^led(-[0-9a-f]+)?$.
Using status as a node name is also confusing since it is commonly used as a
standard device tree property.
Should this be renamed to something like led-status or led-0 to comply with
the schema?
> + linux,default-trigger="heartbeat";
> + max-brightness = <255>;
> + pwms = <&pwm_ao_cd 0 30040 0>;
> + };
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-add-kvim4-sysled-v2-0-3ec9779e8875@aliel.fr?part=3
next prev parent reply other threads:[~2026-05-14 4:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 10:43 [PATCH v2 0/3] Khadas VIM4 PWM status LED support Ronald Claveau via B4 Relay
2026-05-13 10:43 ` [PATCH v2 1/3] arm64: dts: amlogic: t7: Fix pwm_ao_c pinmux definitions Ronald Claveau via B4 Relay
2026-05-13 10:43 ` [PATCH v2 2/3] arm64: dts: amlogic: t7: khadas-vim4: reorder root node Ronald Claveau via B4 Relay
2026-05-13 12:21 ` Neil Armstrong
2026-05-13 10:43 ` [PATCH v2 3/3] arm64: dts: amlogic: t7: khadas-vim4: add PWM-driven status LED Ronald Claveau via B4 Relay
2026-05-13 12:35 ` Neil Armstrong
2026-05-14 4:05 ` sashiko-bot [this message]
2026-05-13 12:37 ` (subset) [PATCH v2 0/3] Khadas VIM4 PWM status LED support Neil Armstrong
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=20260514040520.5FF16C2BCB7@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+linux-kernel-dev.aliel.fr@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=neil.armstrong@linaro.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