diff options
| author | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-08-14 15:09:29 +0200 |
|---|---|---|
| committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-08-17 15:52:01 +0200 |
| commit | be09fdbf36c0a69e7fd024328a793313ae3bafd3 (patch) | |
| tree | 569bd9340800cbfa646ea600b7a55b92e7a17577 /target/linux/ath79/dts/ar7240_buffalo_whr-g301n.dts | |
| parent | 5d3e5d6ccc7654bd98784c9de83de49f3c542577 (diff) | |
| download | upstream-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 ð0/ð1 nodes are enabled together with
the &mdio0/&mdio1 nodes containing the builtin-switch.
For ar7240_tplink_tl-wa.dtsi, ð0 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_buffalo_whr-g301n.dts')
| -rw-r--r-- | target/linux/ath79/dts/ar7240_buffalo_whr-g301n.dts | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/target/linux/ath79/dts/ar7240_buffalo_whr-g301n.dts b/target/linux/ath79/dts/ar7240_buffalo_whr-g301n.dts index 042219b234..84cd969cf3 100644 --- a/target/linux/ath79/dts/ar7240_buffalo_whr-g301n.dts +++ b/target/linux/ath79/dts/ar7240_buffalo_whr-g301n.dts @@ -156,8 +156,6 @@ }; ð0 { - status = "okay"; - mtd-mac-address = <&art 0x120c>; }; |