From: Lee Jones <lee@kernel.org>
To: Astrid Rost <astrid.rost@axis.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh@kernel.org>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
kernel@axis.com, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: leds: Read max-brightness from devicetree
Date: Thu, 13 Jul 2023 14:33:00 +0100 [thread overview]
Message-ID: <20230713133300.GS10768@google.com> (raw)
In-Reply-To: <20230703130313.548519-2-astrid.rost@axis.com>
On Mon, 03 Jul 2023, Astrid Rost wrote:
> Normally, the maximum brightness is determined by the hardware, and this
> property is not required. This property is used to set a software limit.
> It could happen that an LED is made so bright that it gets damaged or
> causes damage due to restrictions in a specific system, such as mounting
> conditions.
> Note that this flag is mainly used for PWM-LEDs, where it is not possible
> to map brightness to current. Drivers for other controllers should use
> led-max-microamp.
>
> Signed-off-by: Astrid Rost <astrid.rost@axis.com>
> ---
> Documentation/devicetree/bindings/leds/common.yaml | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
Applied, thanks
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-07-13 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230703130313.548519-1-astrid.rost@axis.com>
2023-07-03 13:03 ` [PATCH v3 1/2] dt-bindings: leds: Read max-brightness from devicetree Astrid Rost
2023-07-05 6:32 ` Krzysztof Kozlowski
2023-07-05 15:55 ` Rob Herring
2023-07-13 13:33 ` Lee Jones [this message]
2023-07-03 13:03 ` [PATCH v3 2/2] led: led-class: " Astrid Rost
2023-07-03 21:39 ` Jacek Anaszewski
2023-07-13 13:33 ` Lee Jones
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=20230713133300.GS10768@google.com \
--to=lee@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=astrid.rost@axis.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
/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.