diff options
| author | Mathias Kresin <dev@kresin.me> | 2018-08-18 12:07:08 +0200 |
|---|---|---|
| committer | Mathias Kresin <dev@kresin.me> | 2018-08-29 09:39:32 +0200 |
| commit | c134210b8f7e18b43641b6c2176e7a3e6baed030 (patch) | |
| tree | 5964505dec49b986ba4b4817d44e770178dc8e8c /target/linux/apm821xx/patches-4.14/020-0022-crypto-crypto4xx-simplify-sa-and-state-context-acqui.patch | |
| parent | 43df31f64dfc68374093142cd51808655d6e8d50 (diff) | |
| download | upstream-c134210b8f7e18b43641b6c2176e7a3e6baed030.tar.gz upstream-c134210b8f7e18b43641b6c2176e7a3e6baed030.tar.bz2 upstream-c134210b8f7e18b43641b6c2176e7a3e6baed030.zip | |
ramips: drop pointless default led definitions
The LEDs should be triggered/lit by any kind of state change instead of
turned on/off unconditional.
If LEDs really need to be turned off by default, it should be done via
the default-state devicetree led property.
The handling of the wndr3700v5 and wt3020 power led is at least
strange. Something is for sure wrong with them. Either the leds are
misnamed, the default off trigger is a typo or the polarity of the
gpios is wrong. Drop the power led from userspace and wait for someone
with access to the hardware to fix it properly.
Signed-off-by: Mathias Kresin <dev@kresin.me>
Diffstat (limited to 'target/linux/apm821xx/patches-4.14/020-0022-crypto-crypto4xx-simplify-sa-and-state-context-acqui.patch')
0 files changed, 0 insertions, 0 deletions