From: Lee Jones <lee@kernel.org>
To: Lukas Timmermann <linux@timmermann.space>
Cc: pavel@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 2/2] leds: as3668: Driver for the ams Osram 4-channel i2c LED driver
Date: Thu, 20 Nov 2025 13:31:49 +0000 [thread overview]
Message-ID: <20251120133149.GA661940@google.com> (raw)
In-Reply-To: <nkdqizx5lmf5mgovt4lv4pkzzaujnqt4zlhuwdlidrlgyqr5s5@dvnhdhkhfuvy>
On Thu, 20 Nov 2025, Lukas Timmermann wrote:
> On Mon, Nov 17, 2025 at 03:00:08AM +0100, Lukas Timmermann wrote:
> > Since there were no existing drivers for the AS3668 or related devices,
> > a new driver was introduced in a separate file. Similar devices were
> > reviewed, but none shared enough characteristics to justify code reuse.
> > As a result, this driver is written specifically for the AS3668.
> >
> > Signed-off-by: Lukas Timmermann <linux@timmermann.space>
> > ---
> > MAINTAINERS | 1 +
> > drivers/leds/Kconfig | 13 +++
> > drivers/leds/Makefile | 1 +
> > drivers/leds/leds-as3668.c | 222 +++++++++++++++++++++++++++++++++++++
> > 4 files changed, 237 insertions(+)
> > create mode 100644 drivers/leds/leds-as3668.c
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 091206c54c63..945d78fef380 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -3511,6 +3511,7 @@ M: Lukas Timmermann <linux@timmermann.space>
> > L: linux-leds@vger.kernel.org
> > S: Maintained
> > F: Documentation/devicetree/bindings/leds/ams,as3668.yaml
> > +F: drivers/leds/leds-as3668.c
> >
> > ASAHI KASEI AK7375 LENS VOICE COIL DRIVER
> > M: Tianshu Qiu <tian.shu.qiu@intel.com>
> > diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
> > index a104cbb0a001..ec37d55ac14e 100644
> > --- a/drivers/leds/Kconfig
> > +++ b/drivers/leds/Kconfig
> > @@ -100,6 +100,19 @@ config LEDS_ARIEL
> >
> > Say Y to if your machine is a Dell Wyse 3020 thin client.
> >
> > +config LEDS_OSRAM_AMS_AS3668
> I've modified this line as requested in patch series v9. After comparing
> this with other configuration options in drivers/leds/Kconfig, this
> seems out of place. Shouldn't we keep this consistent?
There are a few other examples in there, so consistency is less of an
issue. I personally think it provides a better picture of the device if
the manufacture is mentioned as well.
But this is not a blocking point. Take your preference.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-11-20 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 2:00 [PATCH v10 0/2] Support for Osram as3668 LED driver Lukas Timmermann
2025-11-17 2:00 ` [PATCH v10 1/2] dt-bindings: leds: Add new as3668 support Lukas Timmermann
2025-11-17 2:00 ` [PATCH v10 2/2] leds: as3668: Driver for the ams Osram 4-channel i2c LED driver Lukas Timmermann
2025-11-20 11:43 ` Lukas Timmermann
2025-11-20 13:31 ` Lee Jones [this message]
2025-11-25 11:20 ` Lukas Timmermann
2025-11-20 12:07 ` Lee Jones
2025-11-21 14:05 ` Lukas Timmermann
2025-11-25 12:58 ` 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=20251120133149.GA661940@google.com \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@timmermann.space \
--cc=pavel@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 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).