ARM: dts: BCM53573: Don't use nonexistent "default-off" LED trigger

Such a trigger doesn't exist in Linux and is not needed as LED is being
turned off by default. This could cause errors in LEDs core code when
trying to set default trigger.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>

diff --git a/arch/arm/boot/dts/bcm47189-tenda-ac9.dts b/arch/arm/boot/dts/bcm47189-tenda-ac9.dts
index 6bdd795..34417da 100644 (file)
--- a/arch/arm/boot/dts/bcm47189-tenda-ac9.dts
+++ b/arch/arm/boot/dts/bcm47189-tenda-ac9.dts
@@ -26,19 +26,16 @@
                usb {
                        label = "bcm53xx:blue:usb";
                        gpios = <&chipcommon 1 GPIO_ACTIVE_HIGH>;
-                       linux,default-trigger = "default-off";
                };
 
                wps {
                        label = "bcm53xx:blue:wps";
                        gpios = <&chipcommon 10 GPIO_ACTIVE_HIGH>;
-                       linux,default-trigger = "default-off";
                };
 
                5ghz {
                        label = "bcm53xx:blue:5ghz";
                        gpios = <&chipcommon 11 GPIO_ACTIVE_HIGH>;
-                       linux,default-trigger = "default-off";
                };
 
                system {
@@ -54,7 +51,6 @@
                2ghz {
                        label = "bcm53xx:blue:2ghz";
                        gpios = <&pcie0_chipcommon 3 GPIO_ACTIVE_HIGH>;
-                       linux,default-trigger = "default-off";
                };
        };