231dc26867
The "/dts-v1/;" identifier is supposed to be put once at the beginning of a device tree file. Thus, it makes no sense to provide it a second time in to-be-included DTSI files. This removes the identifier from all DTSI files in /target/linux. Most of the DTS files in OpenWrt do contain the "/dts-v1/;". It is missing for most of the following targets, though: mvebu, ipq806x, mpc85xx, ipq40xx This does not touch ipq806x for now, as the bump to 4.19 is close. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
69 lines
1.2 KiB
Plaintext
69 lines
1.2 KiB
Plaintext
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
|
|
|
|
#include "tp9343_tplink_tl-wr94x.dtsi"
|
|
|
|
/ {
|
|
aliases {
|
|
led-boot = &led_system;
|
|
led-failsafe = &led_system;
|
|
led-running = &led_system;
|
|
led-upgrade = &led_system;
|
|
};
|
|
|
|
leds {
|
|
compatible = "gpio-leds";
|
|
|
|
led_system: system {
|
|
label = "tp-link:blue:system";
|
|
gpios = <&gpio 18 GPIO_ACTIVE_LOW>;
|
|
default-state = "on";
|
|
};
|
|
|
|
qss {
|
|
label = "tp-link:blue:qss";
|
|
gpios = <&gpio 3 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
wlan {
|
|
label = "tp-link:blue:wlan";
|
|
gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
|
|
linux,default-trigger = "phy0tpt";
|
|
};
|
|
|
|
wan_blue {
|
|
label = "tp-link:blue:wan";
|
|
gpios = <&gpio 14 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
wan_red {
|
|
label = "tp-link:red:wan";
|
|
gpios = <&gpio 15 GPIO_ACTIVE_HIGH>;
|
|
};
|
|
|
|
lan1 {
|
|
label = "tp-link:blue:lan1";
|
|
gpios = <&gpio 7 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
lan2 {
|
|
label = "tp-link:blue:lan2";
|
|
gpios = <&gpio 6 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
lan3 {
|
|
label = "tp-link:blue:lan3";
|
|
gpios = <&gpio 5 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
lan4 {
|
|
label = "tp-link:blue:lan4";
|
|
gpios = <&gpio 4 GPIO_ACTIVE_LOW>;
|
|
};
|
|
};
|
|
};
|
|
|
|
ð1 {
|
|
mtd-mac-address = <&uboot 0x1fc00>;
|
|
mtd-mac-address-increment = <(-1)>;
|
|
};
|