Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v1 5/7] ARM: tegra: lg-x3: Add flash LEDs controller node
Date: Thu, 24 Sep 2026 09:16:47 +0000	[thread overview]
Message-ID: <20260924091647.A18F91F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924090608.28734-6-clamor95@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: hw misrepresentation of single flash LED as multiple nodes
--

commit 1c030c2896d9a641e8c683129fc55fbf9766228a
Author: Svyatoslav Ryhel <clamor95@gmail.com>
ARM: tegra: lg-x3: Add flash LEDs controller node

This commit adds a device tree node for the ti lm3559 controller used for
flash leds on the tegra30 lg-x3 device. It configures the controller and
sets up two separate child nodes to represent the flash.

> diff --git a/arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi b/arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi
> index 74583eb07aa84..14d4f992222c6 100644
> --- a/arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi
> +++ b/arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi
[ ... ]
> @@ -1267,6 +1268,35 @@ m24c08: eeprom@50 {
[ ... ]
> +		led-controller@53 {
> +			compatible = "ti,lm3559";
> +			reg = <0x53>;
[ ... ]
> +			/* single flash led is on 2 lines */
> +			lm3559_led0: led@0 {
> +				reg = <0>;
> +
> +				flash-max-microamp = <393750>;
> +				led-max-microamp = <140625>;
> +			};
> +
> +			lm3559_led1: led@1 {
> +				reg = <1>;

[Severity: Medium]
Does this configuration incorrectly define a single physical led as two
independent led devices?

The comment indicates the single flash led is on two lines, but splitting it
into two separate nodes exposes two distinct video4linux2 subdevices. Device
trees generally describe hardware topology rather than driver limitations.

Should this be modeled as a single node using a property like
led-sources = <0 1>? Even if the current driver lacks support for the
led-sources property, duplicating child nodes to work around driver
limitations is considered a device tree anti-pattern.

> +
> +				flash-max-microamp = <393750>;
> +				led-max-microamp = <140625>;
> +			};
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260924090608.28734-1-clamor95@gmail.com?part=5

  reply	other threads:[~2026-09-24  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  9:06 [PATCH v1 0/7] ARM: tegra: lg-x3: Add newly supported devices and fixes Svyatoslav Ryhel
2026-09-24  9:06 ` [PATCH v1 1/7] ARM: tegra: lg-x3: Adjust WiFi node Svyatoslav Ryhel
2026-09-24  9:06 ` [PATCH v1 2/7] ARM: tegra: lg-x3: Remove pinctrl-* properties duplication Svyatoslav Ryhel
2026-09-24  9:06 ` [PATCH v1 3/7] ARM: tegra: lg-x3: Lower supported suspend mode Svyatoslav Ryhel
2026-09-24  9:06 ` [PATCH v1 4/7] ARM: tegra: lg-x3: Add light sensor node Svyatoslav Ryhel
2026-09-24  9:15   ` sashiko-bot
2026-09-24  9:06 ` [PATCH v1 5/7] ARM: tegra: lg-x3: Add flash LEDs controller node Svyatoslav Ryhel
2026-09-24  9:16   ` sashiko-bot [this message]
2026-09-24  9:06 ` [PATCH v1 6/7] ARM: tegra: lg-x3: Add haptic engine node Svyatoslav Ryhel
2026-09-24  9:15   ` sashiko-bot
2026-09-24  9:06 ` [PATCH v1 7/7] ARM: tegra: lg-x3: Add backlight LED controller node Svyatoslav Ryhel
2026-09-24  9:20   ` 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=20260924091647.A18F91F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@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