linux-toradex.git/drivers/leds/trigger/ledtrig-gpio.c, branch v5.5

leds: trigger: gpio: GPIO 0 is valid

2019-09-01T11:33:30+00:00

Allow all valid GPIOs to be used in the driver.

Fixes: 17354bfe8527 ("leds: Add gpio-led trigger")
Signed-off-by: Andy Shevchenko 
Signed-off-by: Jacek Anaszewski

treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 500

2019-06-19T15:09:55+00:00

Based on 2 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license version 2 as
  published by the free software foundation

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license version 2 as
  published by the free software foundation #

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-only

has been chosen to replace the boilerplate/reference in 4122 file(s).

Signed-off-by: Thomas Gleixner 
Reviewed-by: Enrico Weigelt 
Reviewed-by: Kate Stewart 
Reviewed-by: Allison Randal 
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190604081206.933168790@linutronix.de
Signed-off-by: Greg Kroah-Hartman

leds: gpio trigger: simplifications from core changes

2018-07-05T21:21:15+00:00

The trigger core learned error handling for the activate callback and
to handle device attributes. Also make use of the module_led_trigger()
helper to simplify trigger registration.

Signed-off-by: Uwe Kleine-König 
Acked-by: Pavel Machek 
Signed-off-by: Jacek Anaszewski

leds: triggers: let struct led_trigger::activate() return an error code

2018-07-05T21:21:10+00:00

Given that activating a trigger can fail, let the callback return an
indication. This prevents to have a trigger active according to the
"trigger" sysfs attribute but not functional.

All users are changed accordingly to return 0 for now. There is no intended
change in behaviour.

Signed-off-by: Uwe Kleine-König 
Acked-by: Pavel Machek 
Signed-off-by: Jacek Anaszewski

leds: triggers: make the MODULE_LICENSE string match the actual license

2018-07-05T20:59:36+00:00

These files are licensed under GPL version 2 only. So use "GPL v2"
instead of "GPL" (which means v2 or later).

Also remove an empty (but commented) line at the end of the license
header which nicely proves in the context that the drivers are really v2
only :-)

Signed-off-by: Uwe Kleine-König 
Signed-off-by: Jacek Anaszewski

leds: trigger: gpio: Use threaded IRQ

2017-05-29T19:55:58+00:00

This both simplifies the code because we can drop the workqueue
indirection, and it enables using the trigger for GPIOs that work with
threaded IRQs themselves.

Signed-off-by: Jan Kiszka 
Reviewed-by: Andy Shevchenko 
Signed-off-by: Jacek Anaszewski

leds: trigger: gpio: Refresh LED state after GPIO change

2017-05-29T19:55:04+00:00

The new GPIO may have a different state than the old one.

Signed-off-by: Jan Kiszka 
Reviewed-by: Andy Shevchenko 
Signed-off-by: Jacek Anaszewski

leds: core: Add led_set_brightness_nosleep{nopm} functions

2016-01-04T08:57:30+00:00

This patch adds led_set_brightness_nosleep() and led_set_brightness_nopm()
functions, that guarantee setting LED brightness in a non-blocking way.
The latter is used from pm_ops context and doesn't modify the brightness
cached in the struct led_classdev. Its execution always ends up with
a call to brightness setting op - either directly or through
a set_brightness_work, regardless of LED_SUSPENDED flag state.

The patch also replaces led_set_brightness_async() with
led_set_brightness_nosleep() in all places where the most vital was setting
brightness in a non sleeping way but not necessarily asynchronously, which
is not needed for non-blocking drivers.

Signed-off-by: Jacek Anaszewski 
Acked-by: Sakari Ailus

leds: Add support for setting brightness in a synchronous way

2014-11-14T22:29:35+00:00

There are use cases when setting a LED brightness has to
have immediate effect (e.g. setting a torch LED brightness).
This patch extends LED subsystem to support such operations.
The LED subsystem internal API __led_set_brightness is changed
to led_set_brightness_async and new led_set_brightness_sync API
is added.

Signed-off-by: Jacek Anaszewski 
Acked-by: Kyungmin Park 
Cc: Richard Purdie 
Signed-off-by: Bryan Wu

leds: trigger: gpio: fix warning in gpio trigger for gpios whose accessor function may sleep

2014-09-11T23:57:51+00:00

When using a GPIO driver whose accessor functions may sleep (e.g. an
I2C GPIO extender like PCA9554) the following warning is issued:
WARNING: CPU: 0 PID: 665 at drivers/gpio/gpiolib.c:2274 gpiod_get_raw_value+0x3c/0x48()
Modules linked in:
CPU: 0 PID: 665 Comm: kworker/0:2 Not tainted 3.16.0-karo+ #115
Workqueue: events gpio_trig_work
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (warn_slowpath_common+0x64/0x84)
[] (warn_slowpath_common) from [] (warn_slowpath_null+0x1c/0x24)
[] (warn_slowpath_null) from [] (gpiod_get_raw_value+0x3c/0x48)
[] (gpiod_get_raw_value) from [] (gpio_trig_work+0x1c/0xb0)
[] (gpio_trig_work) from [] (process_one_work+0x144/0x38c)
[] (process_one_work) from [] (worker_thread+0x60/0x5cc)
[] (worker_thread) from [] (kthread+0xb4/0xd0)
[] (kthread) from [] (ret_from_fork+0x14/0x24)
---[ end trace cd51a1dad8b86c9c ]---

Fix this by using the _cansleep() variant of gpio_get_value().

Signed-off-by: Lothar Waßmann 
Signed-off-by: Bryan Wu