From: Lee Jones <lee@kernel.org>
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,
bsp-development.geo@leica-geosystems.com
Subject: Re: [PATCH V3 2/2] leds: pwm: Add optional GPIO enable pin support
Date: Thu, 10 Jul 2025 10:37:26 +0100 [thread overview]
Message-ID: <20250710093726.GD1431498@google.com> (raw)
In-Reply-To: <20250703035256.225289-2-Qing-wu.Li@leica-geosystems.com.cn>
On Thu, 03 Jul 2025, LI Qingwu wrote:
> add support for optional GPIO-based enable pin control to PWM LED driver.
> some PWM LED chips have a dedicated enable GPIO. This commit adds the
> support to specify such GPIO, activating the pin when LED brightness
> is non-zero and deactivating it when off.
>
> Signed-off-by: LI Qingwu <Qing-wu.Li@leica-geosystems.com.cn>
> ---
> drivers/leds/leds-pwm.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
Couple of nits.
> diff --git a/drivers/leds/leds-pwm.c b/drivers/leds/leds-pwm.c
> index c73134e7b9514..1397149464b35 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>
>
> struct led_pwm {
> const char *name;
> @@ -29,6 +30,7 @@ struct led_pwm_data {
> struct led_classdev cdev;
> struct pwm_device *pwm;
> struct pwm_state pwmstate;
> + struct gpio_desc *enable_gpio;
> unsigned int active_low;
> };
>
> @@ -51,6 +53,9 @@ static int led_pwm_set(struct led_classdev *led_cdev,
> if (led_dat->active_low)
> duty = led_dat->pwmstate.period - duty;
>
> + gpiod_set_value_cansleep(led_dat->enable_gpio,
> + brightness == LED_OFF ? 0 : 1);
Put this on one line.
> +
> led_dat->pwmstate.duty_cycle = duty;
> /*
> * Disabling a PWM doesn't guarantee that it emits the inactive level.
> @@ -132,6 +137,23 @@ static int led_pwm_add(struct device *dev, struct led_pwm_priv *priv,
> break;
> }
>
> + /* Claim the GPIO as ASIS and set the value
Explain what ASIS is please.
> + * later on to honor the different default states
> + */
Use proper multi-line comments please.
> + led_data->enable_gpio =
> + devm_fwnode_gpiod_get(dev, fwnode, "enable", GPIOD_ASIS, NULL);
One line please.
> +
Drop this line.
> + /* enable_gpio is optional */
Comments start with a capital letter.
Place this comment inside the second if () statement.
> + if (IS_ERR(led_data->enable_gpio)) {
> + if (PTR_ERR(led_data->enable_gpio) == -ENOENT)
> + led_data->enable_gpio = NULL;
> + else
> + return PTR_ERR(led_data->enable_gpio);
> + }
> +
> + gpiod_direction_output(led_data->enable_gpio,
> + !!led_data->cdev.brightness);
One line.
> +
> ret = devm_led_classdev_register_ext(dev, &led_data->cdev, &init_data);
> if (ret) {
> dev_err(dev, "failed to register PWM led for %s: %d\n",
> --
> 2.43.0
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-07-10 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 3:52 [PATCH V3 1/2] dt-bindings: leds: pwm: Add enable-gpios property LI Qingwu
2025-07-03 3:52 ` [PATCH V3 2/2] leds: pwm: Add optional GPIO enable pin support LI Qingwu
2025-07-10 9:37 ` Lee Jones [this message]
2025-07-14 3:32 ` LI Qingwu
2025-07-18 13:23 ` Lee Jones
2025-07-03 7:10 ` [PATCH V3 1/2] dt-bindings: leds: pwm: Add enable-gpios property Krzysztof Kozlowski
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=20250710093726.GD1431498@google.com \
--to=lee@kernel.org \
--cc=Qing-wu.Li@leica-geosystems.com.cn \
--cc=bsp-development.geo@leica-geosystems.com \
--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.