linux-toradex.git/drivers/leds/leds-ns2.c, branch v4.4.10

leds: leds-ns2: Fix module autoload for OF platform driver

2015-09-17T08:02:05+00:00

This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.

Signed-off-by: Luis de Bethencourt 
Signed-off-by: Jacek Anaszewski

leds: leds-ns2: handle can_sleep GPIOs

2015-08-28T12:06:09+00:00

On the board n090401 (Seagate NAS 4-Bay), some of the LEDs are handled
by the leds-ns2 driver. This LEDs are connected to an I2C GPIO expander
(PCA95554PW) which means that GPIO access may sleep. This patch makes
leds-ns2 compatible with such GPIOs by using the *_cansleep() variant of
the GPIO functions. As a drawback this functions can't be used safely in
a timer context (with the timer LED trigger for example). To fix this
issue, a workqueue mechanism (copied from the leds-gpio driver) is used.

Note that this patch also updates slightly the ns2_led_sata_store
function. The LED state is now retrieved from cached values instead of
reading the GPIOs previously. This prevents ns2_led_sata_store from
working with a stale LED state (which may happen when a delayed work
is pending).

Signed-off-by: Simon Guinot 
Signed-off-by: Vincent Donnefort 
Signed-off-by: Jacek Anaszewski

leds: leds-ns2: move LED modes mapping outside of the driver

2015-08-28T12:06:06+00:00

On the board n090401 (Seagate NAS 4-Bay), the LED mode mapping (GPIO
values to LED mode) is different from the one used on other boards
supported by the leds-ns2 driver.

With this patch the hardcoded mapping is removed from leds-ns2. Now,
it must be defined either in the platform data (if an old-fashion board
setup file is used) or in the DT node. In order to allow the later, this
patch also introduces a modes-map property for the leds-ns2 DT binding.

Signed-off-by: Vincent Donnefort 
Signed-off-by: Jacek Anaszewski

leds: drop owner assignment from platform_drivers

2014-10-20T14:20:43+00:00

A platform_driver does not need to set an owner, it will be populated by the
driver core.

Signed-off-by: Wolfram Sang

leds: ns2: fix attribute-creation race

2014-06-25T22:32:11+00:00

Use the attribute groups of the led-class to create the sata attribute
during probe in order to avoid racing with userspace.

Signed-off-by: Johan Hovold 
Signed-off-by: Bryan Wu

drivers/leds: delete non-required instances of include

2014-02-27T17:56:56+00:00

None of these files are actually using any __init type directives
and hence don't need to include .  Most are just a
left over from __devinit and __cpuinit removal, or simply due to
code getting copied from one driver to the next.

Cc: Bryan Wu 
Cc: Richard Purdie 
Cc: linux-leds@vger.kernel.org
Signed-off-by: Paul Gortmaker 
Signed-off-by: Bryan Wu

leds: Include linux/of.h header

2013-10-22T17:57:34+00:00

'of_match_ptr' is defined in linux/of.h. Include it explicitly.

Signed-off-by: Sachin Kamat 
Signed-off-by: Bryan Wu

leds: use dev_get_platdata()

2013-08-27T00:22:11+00:00

Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly.

Signed-off-by: Jingoo Han 
Signed-off-by: Bryan Wu

leds: leds-ns2: remove unnecessary platform_set_drvdata()

2013-06-20T23:21:32+00:00

The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.

Signed-off-by: Jingoo Han 
Signed-off-by: Bryan Wu

leds: leds-ns2: fix oops at module removal

2013-04-01T18:04:52+00:00

This patch fixes a regression introduced by commit 72052fcc10
("leds: leds-ns2: add device tree binding").

When the driver is initialized with device tree data, platform_data
pointer is NULL. This causes a kernel oops at removal.

To fix this bug, num_leds is moved into driver_data and platform_data
is not longer used from ns2_led_remove().

Signed-off-by: Simon Guinot 
Signed-off-by: Bryan Wu