From: Andreas Kemnade <andreas@kemnade.info>
To: pavel@ucw.cz, lee@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, andreas@kemnade.info,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Matti Vaittinen <mazziesaccount@gmail.com>
Subject: [PATCH v6 0/2] leds: Add a driver for the BD2606MVV
Date: Wed, 19 Apr 2023 13:18:04 +0200 [thread overview]
Message-ID: <20230419111806.1100437-1-andreas@kemnade.info> (raw)
Add the binding description and the corresponding driver for
the BD2606.
Changes in V6:
- comments about dealing with shared brightness registers
- comment about building as a module
Changes in V5:
- remove "driver" from the binding subject line
- avoid presenting shared brightness to the userspace
by allowing only on/off in such cases.
Changes in V4:
- minor tuning of description in bindings
Changes in V3:
- binding cleanup
- move active variable from long-living struct onto stack
Changes in V2:
- Add Datasheet link
- use fwnode api
- remove childnode count check, that will bail out
anyways later.
- add enable-gpios to binding but not to driver due to lack of
testing ability
Andreas Kemnade (2):
dt-bindings: leds: Add ROHM BD2606MVV LED
leds: bd2606mvv: Driver for the Rohm 6 Channel i2c LED driver
.../bindings/leds/rohm,bd2606mvv.yaml | 81 +++++++++
drivers/leds/Kconfig | 14 ++
drivers/leds/Makefile | 1 +
drivers/leds/leds-bd2606mvv.c | 160 ++++++++++++++++++
4 files changed, 256 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/rohm,bd2606mvv.yaml
create mode 100644 drivers/leds/leds-bd2606mvv.c
--
2.39.2
next reply other threads:[~2023-04-19 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 11:18 Andreas Kemnade [this message]
2023-04-19 11:18 ` [PATCH v6 1/2] dt-bindings: leds: Add ROHM BD2606MVV LED Andreas Kemnade
2023-04-24 13:16 ` Lee Jones
2023-04-19 11:18 ` [PATCH v6 2/2] leds: bd2606mvv: Driver for the Rohm 6 Channel i2c LED driver Andreas Kemnade
2023-04-24 13:17 ` Lee Jones
2023-04-24 19:06 ` Andreas Kemnade
2023-04-27 16:44 ` 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=20230419111806.1100437-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).