linux/drivers/leds, branch v5.7

leds: core: Fix warning message when init_data

2020-04-06T21:12:08Z

The warning message when a led is renamed due to name collition can fail to show proper original name if init_data is used. Eg: [ 9.073996] leds-gpio a0040000.leds_0: Led (null) renamed to red_led_1 due to name collision Fixes: bb4e9af0348d ("leds: core: Add support for composing LED class device names") Signed-off-by: Ricardo Ribalda Delgado Acked-by: Jacek Anaszewski Signed-off-by: Pavel Machek

leds: sort Makefile entries

2020-04-06T20:57:10Z

Sort Makefile entries to reduce risk of rejects. Signed-off-by: Pavel Machek

leds: ip30: label power LED as such

2020-04-06T20:44:19Z

Make label "white:power" to be consistent with dt-bindings/leds/common.h . Signed-off-by: Pavel Machek

leds: lm3532: make bitfield 'enabled' unsigned

2020-04-06T20:44:18Z

The bitfield 'enabled' should bit unsigned, so make it unsigned. Signed-off-by: Colin Ian King Signed-off-by: Pavel Machek

leds: leds-pwm: Replace zero-length array with flexible-array member

2020-03-21T15:21:16Z

The current codebase makes use of the zero-length array language extension to the C90 standard, but the preferred mechanism to declare variable-length types such as these ones is a flexible array member[1][2], introduced in C99: struct foo { int stuff; struct boo array[]; }; By making use of the mechanism above, we will get a compiler warning in case the flexible array does not occur last in the structure, which will help us prevent some kind of undefined behavior bugs from being inadvertently introduced[3] to the codebase from now on. Also, notice that, dynamic memory allocations won't be affected by this change: "Flexible array members have incomplete type, and so the sizeof operator may not be applied. As a quirk of the original implementation of zero-length arrays, sizeof evaluates to zero."[1] This issue was found with the help of Coccinelle. [1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html [2] https://github.com/KSPP/linux/issues/21 [3] commit 76497732932f ("cxgb3/l2t: Fix undefined behaviour") Signed-off-by: Gustavo A. R. Silva Signed-off-by: Pavel Machek

leds: leds-is31fl32xx: Replace zero-length array with flexible-array member

2020-03-21T15:21:16Z

leds: pwm: remove useless pwm_period_ns

2020-03-21T15:17:53Z

This member seems to was a way to pass PWM period to the LED. Since there is no header anymore, this is useless. Signed-off-by: Denis Osterland-Heim Signed-off-by: Pavel Machek

leds: pwm: remove header

2020-03-21T15:17:53Z

The header is only used by leds_pwm.c, so move contents to leds_pwm.c and remove it. Apply minor changes suggested by checkpatch. Remove deprecated and unused pwm_id member. Suggested-by: Pavel Machek Signed-off-by: Denis Osterland-Heim Signed-off-by: Pavel Machek

leds: pwm: convert to atomic PWM API

2020-02-26T20:49:39Z

pwm_config(), pwm_enable() and pwm_disable() should get removed in the long run. So update the driver to use the atomic API that is here to stay. A few side effects: - led_pwm_set() now returns an error when setting the PWM fails. - During .probe() the PWM isn't disabled implicitly by pwm_apply_args() any more. Signed-off-by: Uwe Kleine-König Tested-by: Jeff LaBundy Signed-off-by: Pavel Machek

leds: pwm: simplify if condition

2020-02-26T20:49:39Z

.pwm_period_ns is an unsigned integer. So when led->pwm_period_ns > 0 is false, we now assign 0 to a value that is already 0, so it doesn't hurt and we can skip checking the actual value. Signed-off-by: Uwe Kleine-König Tested-by: Jeff LaBundy Signed-off-by: Pavel Machek