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>
47 lines
806 B
Plaintext
47 lines
806 B
Plaintext
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
|
|
/dts-v1/;
|
|
|
|
#include <dt-bindings/gpio/gpio.h>
|
|
#include <dt-bindings/input/input.h>
|
|
|
|
#include "qca9558_tplink_archer-c7.dtsi"
|
|
|
|
/ {
|
|
compatible = "tplink,archer-c7-v1", "qca,qca9558";
|
|
model = "TP-Link Archer C7 Version 1";
|
|
};
|
|
|
|
&gpio_keys {
|
|
rfkill {
|
|
gpios = <&gpio 13 GPIO_ACTIVE_LOW>;
|
|
linux,code = <KEY_RFKILL>;
|
|
linux,input-type = <EV_SW>;
|
|
debounce-interval = <60>;
|
|
};
|
|
};
|
|
|
|
&gpio_leds {
|
|
wlan5g {
|
|
label = "tp-link:green:wlan5g";
|
|
gpios = <&gpio 17 GPIO_ACTIVE_LOW>;
|
|
linux,default-trigger = "phy0tpt";
|
|
};
|
|
};
|
|
|
|
&mtdparts {
|
|
uboot: u-boot@0 {
|
|
reg = <0x000000 0x020000>;
|
|
read-only;
|
|
};
|
|
|
|
firmware@20000 {
|
|
compatible = "tplink,firmware";
|
|
reg = <0x020000 0x7d0000>;
|
|
};
|
|
|
|
art: art@7f0000 {
|
|
reg = <0x7f0000 0x010000>;
|
|
read-only;
|
|
};
|
|
};
|