mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dylan Van Assche <me@dylanvanassche.be>
Cc: dmurphy@ti.com, linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] leds: gpio: Set max brightness to 1
Date: Tue, 29 Dec 2020 17:04:50 +0100	[thread overview]
Message-ID: <20201229160450.GA9564@duo.ucw.cz> (raw)
In-Reply-To: <20201229142440.31916-1-me@dylanvanassche.be>

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

Hi!

> GPIO LEDs only know 2 states: ON or OFF and do not have PWM capabilities.
> However, the max brightness is reported as 255.
> 
> This patch sets the max brightness value of a GPIO controlled LED to 1.
> 
> Tested on my PinePhone 1.2.
> 
> Signed-off-by: Dylan Van Assche <me@dylanvanassche.be>
> ---
> v2 drops an obsolete change in include/linux/leds.h

I thought that one looked odd.

> +++ b/drivers/leds/leds-gpio.c
> @@ -96,7 +96,8 @@ static int create_gpio_led(const struct gpio_led *template,
>  	} else {
>  		state = (template->default_state == LEDS_GPIO_DEFSTATE_ON);
>  	}
> -	led_dat->cdev.brightness = state ? LED_FULL : LED_OFF;
> +	led_dat->cdev.brightness = state ? LED_ON : LED_OFF;
> +	led_dat->cdev.max_brightness = LED_ON;

Would simpler version work:

> +	led_dat->cdev.brightness = state;
> +	led_dat->cdev.max_brightness = 1;

? Easier to understand... I'd prefer that version unless it causes
warnings or something.

								Pavel
-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-12-29 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 14:24 Dylan Van Assche
2020-12-29 16:04 ` Pavel Machek [this message]
2020-12-29 18:09   ` Dylan Van Assche

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=20201229160450.GA9564@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=dmurphy@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=me@dylanvanassche.be \
    /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

all inboxes | Powered by JetHome®