From: sashiko-bot@kernel.org
To: "Michiel van Beers" <michielvanbeers@gmail.com>
Cc: linux-leds@vger.kernel.org, lee@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: backlight: lm3630a: Add led-max-microamp
Date: Wed, 11 Nov 2026 16:48:03 +0000 [thread overview]
Message-ID: <sashiko-outbox-209323@kernel.org> (raw)
In-Reply-To: <20261111-lm3630a-led-max-microamp-v2-1-aff11756e7be@gmail.com>
> From: Michiel van Beers <michielvanbeers@gmail.com>
>
> The LM3630A has a full-scale current setting per control bank, from
> 5 mA to 28.25 mA in steps of 750 uA. Boards whose LED strings are rated
> for less than the chip default of 28.25 mA have no way to describe that
> limit.
>
> Add the common led-max-microamp property to the led@0 and led@1 nodes,
> and reference leds/common.yaml from them, where that property is
> defined. The property is optional, so existing devicetrees remain
> valid.
>
> Signed-off-by: Michiel van Beers <michielvanbeers@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111-lm3630a-led-max-microamp-v2-0-aff11756e7be@gmail.com?part=1
next prev parent reply other threads:[~2026-11-11 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 16:21 [PATCH v2 0/2] backlight: lm3630a: Add a per-bank full-scale current limit Michiel van Beers via B4 Relay
2026-11-11 16:21 ` Michiel van Beers
2026-11-11 16:21 ` [PATCH v2 1/2] dt-bindings: backlight: lm3630a: Add led-max-microamp Michiel van Beers via B4 Relay
2026-11-11 16:21 ` Michiel van Beers
2026-11-11 16:48 ` sashiko-bot [this message]
2026-11-12 11:05 ` Krzysztof Kozlowski
2026-11-11 16:21 ` [PATCH v2 2/2] backlight: lm3630a: Allow setting the full-scale current per bank Michiel van Beers via B4 Relay
2026-11-11 16:21 ` Michiel van Beers
2026-11-11 16:50 ` 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=sashiko-outbox-209323@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=michielvanbeers@gmail.com \
--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.