From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: linux-leds@vger.kernel.org
Subject: Re: [PATCH v2] leds: core: avoid error message when a USB LED device is unplugged
Date: Fri, 22 Jan 2016 22:55:48 +0100 [thread overview]
Message-ID: <56A2A564.2030606@gmail.com> (raw)
In-Reply-To: <56A29484.4020307@gmail.com>
On 01/22/2016 09:43 PM, Heiner Kallweit wrote:
> When a USB LED device is unplugged the remove call chain calls
> led_classdev_unregister which tries to switch the LED off.
> As the device has been removed already this results in a ENODEV
> error message in dmesg.
> Avoid this error message by ignoring ENODEV in calls from
> led_classdev_unregister if the LED device is flagged as pluggable.
>
> Therefore a new flag LED_HW_PLUGGABLE was introduced which should be set by
> all LED drivers handling pluggable LED devices (mainly USB LED devices).
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> v2:
> - rebased
> ---
> drivers/leds/led-class.c | 2 ++
> drivers/leds/led-core.c | 5 ++++-
> include/linux/leds.h | 2 ++
> 3 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
> index 14139c3..aa84e5b 100644
> --- a/drivers/leds/led-class.c
> +++ b/drivers/leds/led-class.c
> @@ -245,6 +245,8 @@ void led_classdev_unregister(struct led_classdev *led_cdev)
> up_write(&led_cdev->trigger_lock);
> #endif
>
> + led_cdev->flags |= LED_UNREGISTERING;
> +
> /* Stop blinking */
> led_stop_software_blink(led_cdev);
>
> diff --git a/drivers/leds/led-core.c b/drivers/leds/led-core.c
> index 19e1e60..ad684b6 100644
> --- a/drivers/leds/led-core.c
> +++ b/drivers/leds/led-core.c
> @@ -98,7 +98,10 @@ static void set_brightness_delayed(struct work_struct *ws)
> led_cdev->delayed_set_value);
> else
> ret = -ENOTSUPP;
> - if (ret < 0)
> + 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)))
> dev_err(led_cdev->dev,
> "Setting an LED's brightness failed (%d)\n", ret);
> }
> diff --git a/include/linux/leds.h b/include/linux/leds.h
> index e3470e7..f203a8f 100644
> --- a/include/linux/leds.h
> +++ b/include/linux/leds.h
> @@ -39,6 +39,7 @@ struct led_classdev {
>
> /* Lower 16 bits reflect status */
> #define LED_SUSPENDED (1 << 0)
> +#define LED_UNREGISTERING (1 << 1)
> /* Upper 16 bits reflect control information */
> #define LED_CORE_SUSPENDRESUME (1 << 16)
> #define LED_BLINK_ONESHOT (1 << 17)
> @@ -48,6 +49,7 @@ struct led_classdev {
> #define LED_BLINK_DISABLE (1 << 21)
> #define LED_SYSFS_DISABLE (1 << 22)
> #define LED_DEV_CAP_FLASH (1 << 23)
> +#define LED_HW_PLUGGABLE (1 << 24)
>
> /* Set LED brightness level
> * Must not sleep. Use brightness_set_blocking for drivers
>
Applied to devel branch, thanks.
--
Best Regards,
Jacek Anaszewski
prev parent reply other threads:[~2016-01-22 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 20:43 [PATCH v2] leds: core: avoid error message when a USB LED device is unplugged Heiner Kallweit
2016-01-22 21:55 ` Jacek Anaszewski [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=56A2A564.2030606@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.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).