summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/kirkwood-iconnect.dts
diff options
context:
space:
mode:
authorJason Cooper <jason@lakedaemon.net>2013-10-14 17:37:55 +0000
committerJason Cooper <jason@lakedaemon.net>2013-11-23 17:34:40 +0000
commitdcdf14c729cb0e9d444a3ebdf76a88fb4f325309 (patch)
tree2e66acbe366edeeb4f1149f15782cd05325e5cee /arch/arm/boot/dts/kirkwood-iconnect.dts
parent6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae (diff)
ARM: mvebu: dts: remove unneeded linux,default-state from led nodes
Generally, power LEDs should indicate when power is applied, and go out once power is removed. _Not_ annoy the developer with migraine-inducing blinking reminicent of some badly animated television series designed to sell sugar to children. On a more serious note, most of these OS-specific properties aren't necessary and should be removed. I left two that are legitimately tying disk LEDs to disk activity. Other than that, we keep the state the bootloader left them in until userspace changes the state via sysfs. Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/boot/dts/kirkwood-iconnect.dts')
-rw-r--r--arch/arm/boot/dts/kirkwood-iconnect.dts4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/boot/dts/kirkwood-iconnect.dts b/arch/arm/boot/dts/kirkwood-iconnect.dts
index 4a62b206f680..399fb0caf5ab 100644
--- a/arch/arm/boot/dts/kirkwood-iconnect.dts
+++ b/arch/arm/boot/dts/kirkwood-iconnect.dts
@@ -95,12 +95,12 @@
led-level {
label = "led_level";
gpios = <&gpio1 9 0>;
- linux,default-trigger = "default-on";
+ default-state = "on";
};
power-blue {
label = "power:blue";
gpios = <&gpio1 10 0>;
- linux,default-trigger = "timer";
+ default-state = "keep";
};
power-red {
label = "power:red";