linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
	linux-leds@vger.kernel.org,
	Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH 1/1] leds: core: Omit set_brightness error message for a LED supporting hw trigger only
Date: Thu, 20 Jun 2024 10:09:32 +0100	[thread overview]
Message-ID: <20240620090932.GD3029315@google.com> (raw)
In-Reply-To: <20240613075712.2479669-1-lee@kernel.org>

On Thu, 13 Jun 2024, Lee Jones wrote:

> If both set_brightness functions return -ENOTSUPP, then the LED doesn't
> support setting a fixed brightness value, and the error message isn't
> helpful. This can be the case e.g. for LEDs supporting a specific hw
> trigger only.
> 
> Pinched the subject line and commit message from Heiner:
> Link: https://lore.kernel.org/all/44177e37-9512-4044-8991-bb23b184bf37@gmail.com/
> 
> Reworked the function to provide Heiner's required semantics whilst
> simultaneously increasing readability and flow.
> 
> Cc: Pavel Machek <pavel@ucw.cz>
> Cc: linux-leds@vger.kernel.org
> Suggested-by: Heiner Kallweit <hkallweit1@gmail.com>

Heiner, you good with this solution?

A Tested-by or Reviewed-by would be good if you have the time.

> Signed-off-by: Lee Jones <lee@kernel.org>
> ---
>  drivers/leds/led-core.c | 19 +++++++++++++------
>  1 file changed, 13 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/leds/led-core.c b/drivers/leds/led-core.c
> index ef7d1c6767ca..3b4db39f2326 100644
> --- a/drivers/leds/led-core.c
> +++ b/drivers/leds/led-core.c
> @@ -123,15 +123,22 @@ static void led_timer_function(struct timer_list *t)
>  static void set_brightness_delayed_set_brightness(struct led_classdev *led_cdev,
>  						  unsigned int value)
>  {
> -	int ret = 0;
> +	int ret;
>  
>  	ret = __led_set_brightness(led_cdev, value);
> -	if (ret == -ENOTSUPP)
> +	if (ret == -ENOTSUPP) {
>  		ret = __led_set_brightness_blocking(led_cdev, value);
> -	if (ret < 0 &&
> -	    /* LED HW might have been unplugged, therefore don't warn */
> -	    !(ret == -ENODEV && (led_cdev->flags & LED_UNREGISTERING) &&
> -	    (led_cdev->flags & LED_HW_PLUGGABLE)))
> +		if (ret == -ENOTSUPP)
> +			/* No back-end support to set a fixed brightness value */
> +			return;
> +	}
> +
> +	/* LED HW might have been unplugged, therefore don't warn */
> +	if (ret == -ENODEV && led_cdev->flags & LED_UNREGISTERING &&
> +	    led_cdev->flags & LED_HW_PLUGGABLE)
> +		return;
> +
> +	if (ret < 0)
>  		dev_err(led_cdev->dev,
>  			"Setting an LED's brightness failed (%d)\n", ret);
>  }
> -- 
> 2.45.2.505.gda0bf45e8d-goog
> 

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2024-06-20  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  7:57 [PATCH 1/1] leds: core: Omit set_brightness error message for a LED supporting hw trigger only Lee Jones
2024-06-20  9:09 ` Lee Jones [this message]
2024-06-24 20:21   ` Heiner Kallweit
2024-06-26 15:56     ` 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=20240620090932.GD3029315@google.com \
    --to=lee@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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).