All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: LI Qingwu <Qing-wu.Li@leica-geosystems.com.cn>
Cc: "pavel@kernel.org" <pavel@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V8 2/2] leds: pwm: Add optional GPIO enable pin support
Date: Tue, 2 Sep 2025 11:26:36 +0100	[thread overview]
Message-ID: <20250902102636.GF2163762@google.com> (raw)
In-Reply-To: <PAXPR06MB7966CCA6E36625F3F807DA2BD72BA@PAXPR06MB7966.eurprd06.prod.outlook.com>

On Tue, 12 Aug 2025, LI Qingwu wrote:

> 
> 
> > -----Original Message-----
> > From: Lee Jones <lee@kernel.org>
> > Sent: Thursday, July 31, 2025 6:46 PM
> > To: LI Qingwu <Qing-wu.Li@leica-geosystems.com.cn>
> > 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 V8 2/2] leds: pwm: Add optional GPIO enable pin support
> > 
> > 
> > On Thu, 24 Jul 2025, LI Qingwu wrote:
> > 
> > > Add support for optional GPIO-based enable pin control to PWM LED driver.
> > > Some PWM LED driver chips like TPS92380 and LT3743 require a separate
> > > enable signal in addition to PWM control. Implement support for such
> > > GPIO control through the "enable-gpios" device tree property,
> > > activating the pin when LED brightness is non-zero and deactivating it when
> > off.
> > >
> > > Tested on i.MX8MP EVK with TPS92380 LED driver chip
> > >
> > > Signed-off-by: LI Qingwu <Qing-wu.Li@leica-geosystems.com.cn>
> > > ---
> > >  drivers/leds/leds-pwm.c | 20 ++++++++++++++++++++
> > >  1 file changed, 20 insertions(+)
> > >
> > > diff --git a/drivers/leds/leds-pwm.c b/drivers/leds/leds-pwm.c index
> > > c73134e7b9514..08a1f735166ad 100644
> > > --- a/drivers/leds/leds-pwm.c
> > > +++ b/drivers/leds/leds-pwm.c
> > > @@ -17,6 +17,7 @@
> > >  #include <linux/err.h>
> > >  #include <linux/pwm.h>
> > >  #include <linux/slab.h>
> > > +#include <linux/gpio/consumer.h>
> > 
> > This list is alphabetical.
> > 
> The original code's include order is not alphabetical,
> If you prefer, I can reorder all or just put "#include <linux/gpio/consumer.h>" to first line,
> Please let me know your preference.

First line is okay for now.

Then, if you feel like it, submit another patch to place them in order.

-- 
Lee Jones [李琼斯]

      reply	other threads:[~2025-09-02 10:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24  8:02 [PATCH V8 0/2] leds: pwm: Add optional GPIO enable pin support LI Qingwu
2025-07-24  8:02 ` [PATCH V8 1/2] dt-bindings: leds: pwm: Add enable-gpios property LI Qingwu
2025-07-24  8:02 ` [PATCH V8 2/2] leds: pwm: Add optional GPIO enable pin support LI Qingwu
2025-07-31 10:46   ` Lee Jones
2025-08-12 11:44     ` LI Qingwu
2025-09-02 10:26       ` Lee Jones [this message]

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=20250902102636.GF2163762@google.com \
    --to=lee@kernel.org \
    --cc=Qing-wu.Li@leica-geosystems.com.cn \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.