aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/NBG-419N.dts
diff options
context:
space:
mode:
authorPetr Štetiar <ynezz@true.cz>2018-12-16 12:26:34 +0100
committerJohn Crispin <john@phrozen.org>2018-12-17 08:16:28 +0100
commit0d23fd2ab29a66f5d03187db4fac3e396b4f3b62 (patch)
tree7c87df83ddd40d2c94a3e41bdf1fe0d69949346c /target/linux/ramips/dts/NBG-419N.dts
parent1e4ee63cc8d1889a78b539a5ed7be8d56e9b976f (diff)
downloadupstream-0d23fd2ab29a66f5d03187db4fac3e396b4f3b62.tar.gz
upstream-0d23fd2ab29a66f5d03187db4fac3e396b4f3b62.tar.bz2
upstream-0d23fd2ab29a66f5d03187db4fac3e396b4f3b62.zip
treewide: dts: Remove default-state=off property from all gpio LED nodes
>From the Documentation/devicetree/bindings/leds/common.txt: - default-state : The initial state of the LED. Valid values are "on", "off", and "keep". If the LED is already on or off and the default-state property is set the to same value, then no glitch should be produced where the LED momentarily turns off (or on). The "keep" setting will keep the LED at whatever its current state is, without producing a glitch. The default is off if this property is not present. So setting the default-state of the LEDs to `off` is redundant as `off` is default LED state anyway. We should remove it as almost every new PR/patch submission contains this property by default which seems to be just copy&paste from some DTS file already present in the tree. Signed-off-by: Petr Štetiar <ynezz@true.cz>
Diffstat (limited to 'target/linux/ramips/dts/NBG-419N.dts')
0 files changed, 0 insertions, 0 deletions