[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <168857252930.694223.17559633375471869114.robh@kernel.org>
Date: Wed, 5 Jul 2023 09:55:29 -0600
From: Rob Herring <robh@...nel.org>
To: Astrid Rost <astrid.rost@...s.com>
Cc: Conor Dooley <conor+dt@...nel.org>, linux-kernel@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-leds@...r.kernel.org,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>,
Lee Jones <lee@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
devicetree@...r.kernel.org, kernel@...s.com
Subject: Re: [PATCH v3 1/2] dt-bindings: leds: Read max-brightness from
devicetree
On Mon, 03 Jul 2023 15:03:12 +0200, 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@...s.com>
> ---
> Documentation/devicetree/bindings/leds/common.yaml | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists