From: Andreas Kemnade <andreas@kemnade.info>
To: Lee Jones <lee@kernel.org>
Cc: pavel@ucw.cz, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Matti Vaittinen <mazziesaccount@gmail.com>
Subject: Re: [PATCH v6 2/2] leds: bd2606mvv: Driver for the Rohm 6 Channel i2c LED driver
Date: Mon, 24 Apr 2023 21:06:34 +0200 [thread overview]
Message-ID: <20230424210634.70c26688@aktux> (raw)
In-Reply-To: <20230424131740.GE50521@google.com>
On Mon, 24 Apr 2023 14:17:40 +0100
Lee Jones <lee@kernel.org> wrote:
> On Wed, 19 Apr 2023, Andreas Kemnade wrote:
>
> > The device provides 6 channels which can be individually
> > turned off and on but groups of two channels share a common brightness
> > register.
> >
> > Limitation: The GPIO to enable the device is not used yet.
> >
> > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
> > Acked-by: Pavel Machek <pavel@ucw.cz>
> > ---
> > drivers/leds/Kconfig | 14 +++
> > drivers/leds/Makefile | 1 +
> > drivers/leds/leds-bd2606mvv.c | 160 ++++++++++++++++++++++++++++++++++
> > 3 files changed, 175 insertions(+)
> > create mode 100644 drivers/leds/leds-bd2606mvv.c
>
> Applied, thanks
>
contrary to the binding doc, it does not appear on
https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git/log/?h=for-leds-next
Any problems with applying it?
Regards,
Andreas
next prev parent reply other threads:[~2023-04-24 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 11:18 [PATCH v6 0/2] leds: Add a driver for the BD2606MVV Andreas Kemnade
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 [this message]
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=20230424210634.70c26688@aktux \
--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).