diff options
| author | Markus Hofstaetter <markus.hofstaetter@ait.ac.at> | 2015-11-11 12:40:29 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-12-13 09:21:30 +0100 |
| commit | c5cc3e038d083515e6112707f7ffcdf0e5aa8497 (patch) | |
| tree | a35aced606f86baa870d4b9745d25c47148d2ed1 /net/rfkill | |
| parent | 5403677a46a8155ad369e3ca17c9cc6a037b258e (diff) | |
leds: call led_pwm_set() in leds-pwm to enforce default LED_OFF
commit f16703360da7731a057df2ffa902306819c22398 upstream.
Some PWMs are disabled by default or the default pin setting
does not match the LED_OFF state (e.g., active-low leds).
Hence, the driver may end up reporting 0 brightness, but
the leds are actually on using full brightness, because
it never enforces its default configuration.
So enforce it by calling led_pwm_set() after successfully
registering the device.
Tested on a Phytec phyFLEX i.MX6Q board based on kernel
v3.19.5.
Signed-off-by: Markus Hofstaetter <markus.hofstaetter@ait.ac.at>
Tested-by: Markus Hofstaetter <markus.hofstaetter@ait.ac.at>
Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/rfkill')
0 files changed, 0 insertions, 0 deletions