0d23fd2ab2
>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>
41 lines
638 B
Plaintext
41 lines
638 B
Plaintext
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
|
|
|
|
#include "ar7241_tplink.dtsi"
|
|
|
|
/ {
|
|
gpio-export {
|
|
compatible = "gpio-export";
|
|
#size-cells = <0>;
|
|
|
|
gpio_usb_power {
|
|
gpio-export,name = "tp-link:power:usb";
|
|
gpio-export,output = <1>;
|
|
gpios = <&gpio 6 GPIO_ACTIVE_HIGH>;
|
|
};
|
|
};
|
|
};
|
|
|
|
&gpio_leds {
|
|
led3g {
|
|
label = "tp-link:green:3g";
|
|
gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
|
|
trigger-sources = <&hub_port>;
|
|
linux,default-trigger = "usbport";
|
|
};
|
|
};
|
|
|
|
&usb {
|
|
#address-cells = <1>;
|
|
#size-cells = <0>;
|
|
status = "okay";
|
|
|
|
hub_port: port@1 {
|
|
reg = <1>;
|
|
#trigger-source-cells = <0>;
|
|
};
|
|
};
|
|
|
|
&usb_phy {
|
|
status = "okay";
|
|
};
|