All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Fabio Estevam" <festevam@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Keep rk3399-roc-pc-plus work LED on
Date: Fri, 17 Jul 2026 01:12:23 +0000	[thread overview]
Message-ID: <20260717011223.C24A71F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260717010736.578419-3-festevam@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message describes the work LED as a "prominent blue front-panel status LED", but the patch fails to override the inherited "green:work" label, resulting in a code and commit message mismatch.
--

--- Patch [3]: [PATCH 3/3] arm64: dts: rockchip: Keep rk3399-roc-pc-plus work LED on ---
commit 7bd9a09829c15f03ac88e155bb13da9235dada8c
Author: Fabio Estevam <festevam@nabladev.com>

arm64: dts: rockchip: Keep rk3399-roc-pc-plus work LED on
    
This commit overrides the default LED trigger for the rk3399-roc-pc-plus
work LED to default-on. It changes the behavior from a distracting continuous
blink to a steady status indication.

> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-roc-pc-plus.dts b/arch/arm64/boot/dts/rockchip/rk3399-roc-pc-plus.dts
> index f87bc7b6afc14..7e8039b19be7e 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-roc-pc-plus.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-roc-pc-plus.dts
> @@ -93,6 +93,10 @@ leds {
>  	};
>  };
>  
> +&work_led {
> +	linux,default-trigger = "default-on";
> +};

[Severity: Medium]
The commit message mentions this is the prominent blue front-panel status LED.
Since the board inherits from rk3399-roc-pc.dtsi where the work LED is
typically configured with the green:work label, does this node also need a
color or label override?

If the inherited label is not overridden here, the sysfs interface might
misrepresent the physical blue LED as green, causing a mismatch between the
commit message's description and the resulting device tree.

> +
>  &fusb0 {
>  	vbus-supply = <&vcc_vbus_typec1>;
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260717010736.578419-1-festevam@gmail.com?part=3

      reply	other threads:[~2026-07-17  1:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  1:07 [PATCH 1/3] arm64: dts: rockchip: Fix rk3399-roc-pc-plus analog audio Fabio Estevam
2026-07-17  1:07 ` Fabio Estevam
2026-07-17  1:07 ` [PATCH 2/3] arm64: dts: rockchip: Enable wireless on rk3399-roc-pc-plus Fabio Estevam
2026-07-17  1:07   ` Fabio Estevam
2026-07-17  1:16   ` sashiko-bot
2026-07-17  1:07 ` [PATCH 3/3] arm64: dts: rockchip: Keep rk3399-roc-pc-plus work LED on Fabio Estevam
2026-07-17  1:07   ` Fabio Estevam
2026-07-17  1:12   ` sashiko-bot [this message]

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=20260717011223.C24A71F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.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.