From: George Stark <gnstark@salutedevices.com>
To: <pavel@ucw.cz>, <lee@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <linux-leds@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel@salutedevices.com>,
George Stark <gnstark@salutedevices.com>
Subject: [PATCH v2 0/2] leds: pwm: Add default-brightness property
Date: Fri, 1 Nov 2024 18:48:42 +0300 [thread overview]
Message-ID: <20241101154844.1175860-1-gnstark@salutedevices.com> (raw)
led-pwm driver supports default-state DT property and if that state is on then
the driver during initialization turns on the LED setting maximum brightness.
Sometimes it's desirable to use lower initial brightness.
This patch series adds support for DT property default-brightness.
Things to discuss:
If such a property is acceptable it could be moved to leds/common.yaml due to
several drivers support multiple brightness levels and could support the property
too.
Changes in v2:
leds: pwm: Add optional DT property default-brightness
- refactor patch to make it more accurate
link to v1: [1]
[1] https://lore.kernel.org/lkml/20241015151410.2158102-3-gnstark@salutedevices.com/T/
George Stark (2):
dt-bindings: leds: pwm: Add default-brightness property
leds: pwm: Add optional DT property default-brightness
.../devicetree/bindings/leds/leds-pwm.yaml | 6 ++++++
drivers/leds/leds-pwm.c | 17 ++++++++++++++++-
2 files changed, 22 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2024-11-01 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 15:48 George Stark [this message]
2024-11-01 15:48 ` [PATCH v2 1/2] dt-bindings: " George Stark
2024-11-02 13:06 ` Krzysztof Kozlowski
2024-11-02 23:15 ` George Stark
2024-11-05 15:57 ` Lee Jones
2024-11-01 15:48 ` [PATCH v2 2/2] leds: pwm: Add optional DT property default-brightness George Stark
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=20241101154844.1175860-1-gnstark@salutedevices.com \
--to=gnstark@salutedevices.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@salutedevices.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®