aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ath79/dts/ar7240.dtsi
diff options
context:
space:
mode:
authorAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-08-14 15:09:29 +0200
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-08-17 15:52:01 +0200
commitbe09fdbf36c0a69e7fd024328a793313ae3bafd3 (patch)
tree569bd9340800cbfa646ea600b7a55b92e7a17577 /target/linux/ath79/dts/ar7240.dtsi
parent5d3e5d6ccc7654bd98784c9de83de49f3c542577 (diff)
downloadupstream-be09fdbf36c0a69e7fd024328a793313ae3bafd3.tar.gz
upstream-be09fdbf36c0a69e7fd024328a793313ae3bafd3.tar.bz2
upstream-be09fdbf36c0a69e7fd024328a793313ae3bafd3.zip
ath79: ar724x: make sure builtin-switch is enabled in DT
On ar7240/ar7241 the mdioX node with the builtin-switch is enabled in the DTSI files, but the parent ethX node is left disabled. It only gets enabled per device or device family, and has not been enabled at all yet for the TP-Link WA devices with ar7240, making the switch unavailable there. This patch makes sure &eth0/&eth1 nodes are enabled together with the &mdio0/&mdio1 nodes containing the builtin-switch. For ar7240_tplink_tl-wa.dtsi, &eth0 is properly hidden again via compatible = "syscon", "simple-mfd"; This partially fixes FS#2887, however it seems dmesg still does not show cable (dis)connect in dmesg for ar7240 TP-Link WA devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 8484a764df20cdd673c74b583bfbf71e10c02726)
Diffstat (limited to 'target/linux/ath79/dts/ar7240.dtsi')
-rw-r--r--target/linux/ath79/dts/ar7240.dtsi2
1 files changed, 2 insertions, 0 deletions
diff --git a/target/linux/ath79/dts/ar7240.dtsi b/target/linux/ath79/dts/ar7240.dtsi
index 268c8780f4..301ae67323 100644
--- a/target/linux/ath79/dts/ar7240.dtsi
+++ b/target/linux/ath79/dts/ar7240.dtsi
@@ -59,6 +59,8 @@
};
&eth0 {
+ status = "okay";
+
compatible = "qca,ar7240-eth", "syscon";
pll-data = <0x00110000 0x00001099 0x00991099>;