From: sashiko-bot@kernel.org
To: "Rillian Grant" <rillian.grant@gmail.com>
Cc: devicetree@vger.kernel.org, lee@kernel.org,
linux-leds@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 3/4] leds: flash: lm3643: Describe the LED of ACPI boards without LED nodes
Date: Mon, 28 Sep 2026 09:50:14 +0000 [thread overview]
Message-ID: <20260928095015.096591F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260928094302.86966-4-rillian.grant@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] leds: lm3643: informational logging during probe violates subsystem guidelines
--
commit 526bd68dbe5899ef1f96b678f6b5d764ba338f79
Author: Ruslan Koreev <koreev.r@gmail.com>
leds: flash: lm3643: Describe the LED of ACPI boards without LED nodes
This commit adds a DMI table to describe the LM3643 LED setup on Lenovo
ThinkPads that lack proper firmware descriptions (no _DSD). It provides
a software node configuration to drive the Windows Hello IR flood
illuminator.
> diff --git a/drivers/leds/flash/leds-lm3643.c b/drivers/leds/flash/leds-lm3643.c
> index bbe9358c9caaf..1c0de38ebcdf4 100644
> --- a/drivers/leds/flash/leds-lm3643.c
> +++ b/drivers/leds/flash/leds-lm3643.c
[ ... ]
> @@ -690,6 +691,92 @@ static int lm3643_register_led(struct device *dev, struct lm3643 *chip,
[ ... ]
> +static int lm3643_add_dmi_leds(struct device *dev)
> +{
[ ... ]
> + ret = software_node_register_node_group(nodes);
> + if (ret)
> + return dev_err_probe(dev, ret, "failed to register the LED description\n");
> +
> + set_secondary_fwnode(dev, software_node_fwnode(nodes[0]));
> + dev_info(dev, "no LED nodes in firmware, using the DMI description\n");
[Severity: Low]
Does this informational log message violate the LED subsystem guidelines?
The subsystem rules strictly mandate: "Only log errors or warnings." Since this
call to dev_info() executes automatically in lm3643_add_dmi_leds() during
hardware enumeration on matching laptops, it will add unnecessary minor log
noise during boot.
> +
> + return devm_add_action_or_reset(dev, lm3643_remove_dmi_leds, dev);
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260928094302.86966-1-rillian.grant@gmail.com?part=3
next prev parent reply other threads:[~2026-09-28 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 9:42 [PATCH v2 0/4] leds: flash: LM3643 dual LED flash driver Rillian Grant
2026-09-28 9:42 ` [PATCH v2 1/4] dt-bindings: leds: Document TI " Rillian Grant
2026-09-28 9:49 ` sashiko-bot
2026-10-01 6:34 ` Krzysztof Kozlowski
2026-09-28 9:42 ` [PATCH v2 2/4] leds: flash: Add support for the " Rillian Grant
2026-09-28 9:54 ` sashiko-bot
2026-09-28 9:42 ` [PATCH v2 3/4] leds: flash: lm3643: Describe the LED of ACPI boards without LED nodes Rillian Grant
2026-09-28 9:50 ` sashiko-bot [this message]
2026-09-28 10:08 ` Rillian Grant
2026-09-28 9:42 ` [PATCH v2 4/4] leds: flash: lm3643: Describe the LED on the Lenovo ThinkPad X9-15 Gen 1 Rillian Grant
2026-09-28 9:49 ` sashiko-bot
2026-09-29 9:29 ` [PATCH v2 0/4] leds: flash: LM3643 dual LED flash driver Ruslan Koreev
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=20260928095015.096591F000FF@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=rillian.grant@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.