linux-toradex.git/drivers/leds/leds.h, branch v5.0

leds: triggers: Allow to switch the trigger to "panic" on a kernel panic

2016-05-06T08:22:09+00:00

This commit adds a new led_cdev flag LED_PANIC_INDICATOR, which
allows to mark a specific LED to be switched to the "panic"
trigger, on a kernel panic.

This is useful to allow the user to assign a regular trigger
to a given LED, and still blink that LED on a kernel panic.

Signed-off-by: Ezequiel Garcia 
Reviewed-by: Matthias Brugger 
Acked-by: Pavel Machek 
Signed-off-by: Jacek Anaszewski

leds: core: Drivers shouldn't enforce SYNC/ASYNC brightness setting

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

This patch removes SET_BRIGHTNESS_ASYNC and SET_BRIGHTNESS_SYNC flags.
led_set_brightness() now calls led_set_brightness_nosleep() instead of
choosing between sync and async op basing on the flags defined by the
driver.

From now on, if a user wants to make sure that brightness will be set
synchronously, they have to use led_set_brightness_sync() API. It is now
being made publicly available since it has become apparent that it is
a caller who should decide whether brightness is to be set in
a synchronous or an asynchronous way.

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

leds: core: Use set_brightness_work for the blocking op

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

This patch makes LED core capable of setting brightness for drivers
that implement brightness_set_blocking op. It removes from LED class
drivers responsibility for using work queues on their own.

In order to achieve this set_brightness_delayed callback is being
modified to directly call one of available ops for brightness setting.

led_set_brightness_async() function didn't set brightness in an
asynchronous way in all cases. It was mistakenly assuming that all
LED subsystem drivers used work queue in their brightness_set op,
whereas only half of them did that. Since it has no users now,
it is being removed.

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

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: Rename brightness_set_sync op to brightness_set_blocking

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

The initial purpose of brightness_set_sync op, introduced along with
the LED flash class extension, was to add a means for setting torch LED
brightness as soon as possible, which couldn't have been guaranteed by
brightness_set op. This patch renames the op to brightness_set_blocking,
which describes its purpose in a more generic way. It is beneficial
in view of the prospective changes in the LED core, aiming at removing
the need for using work queues in LED class drivers that can sleep
or use delays while setting brightness.

Signed-off-by: Jacek Anaszewski 
Acked-by: Andrew Lunn 
Acked-by: Pavel Machek 
Acked-by: Sakari Ailus

leds: core: Move LED core callbacks out of led-class.c

2015-11-03T07:59:22+00:00

Since the API for controlling LED brightness and blinking is defined in
the LED core, move the related timer and work callbacks to the led-core.c,
and initialize them through a new led_core_init API.

Signed-off-by: Jacek Anaszewski 
Acked-by: Andrew Lunn 
Acked-by: Pavel Machek

leds: unify the location of led-trigger API

2015-05-04T18:05:55+00:00

Part of led-trigger API was in the private drivers/leds/leds.h header.
Move it to the include/linux/leds.h header to unify the API location
and announce it as public. It has been already exported from
led-triggers.c with EXPORT_SYMBOL_GPL macro. The no-op definitions are
changed from macros to inline to match the style of the surrounding code.

Signed-off-by: Jacek Anaszewski 
Cc: Richard Purdie 
Acked-by: Sakari Ailus 
Signed-off-by: Bryan Wu

leds: Don't allow brightness values greater than max_brightness

2015-01-14T18:40:19+00:00

Since commit 4d71a4a12b13 ("leds: Add support for setting brightness in
a synchronous way") the value passed to brightness_set() is no longer
limited to max_brightness and can be different from the internally saved
brightness value.

Signed-off-by: Gabriele Mazzotta 
Signed-off-by: Bryan Wu

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: delay led_set_brightness if stopping soft-blink

2012-09-11T10:32:40+00:00

Delay execution of led_set_brightness() if need to stop soft-blink
timer.

This allows led_set_brightness to be called in hard-irq context even if
soft-blink was activated on that LED.

Signed-off-by: Fabio Baltieri 
Cc: Pawel Moll 
Signed-off-by: Bryan Wu