@@ -24,56 +24,46 @@ description: |
2424
2525 There is only the standalone version of MT7531.
2626
27- Port 5 on MT7530 has got various ways of configuration.
28-
29- For standalone MT7530:
27+ Port 5 on MT7530 has got various ways of configuration:
3028
3129 - Port 5 can be used as a CPU port.
3230
33- - PHY 0 or 4 of the switch can be muxed to connect to the gmac of the SoC
34- which port 5 is wired to. Usually used for connecting the wan port
35- directly to the CPU to achieve 2 Gbps routing in total.
31+ - PHY 0 or 4 of the switch can be muxed to gmac5 of the switch. Therefore,
32+ the gmac of the SoC which is wired to port 5 can connect to the PHY.
33+ This is usually used for connecting the wan port directly to the CPU to
34+ achieve 2 Gbps routing in total.
3635
37- The driver looks up the reg on the ethernet-phy node which the phy-handle
38- property refers to on the gmac node to mux the specified phy.
36+ The driver looks up the reg on the ethernet-phy node, which the phy-handle
37+ property on the gmac node refers to, to mux the specified phy.
3938
4039 The driver requires the gmac of the SoC to have "mediatek,eth-mac" as the
41- compatible string and the reg must be 1. So, for now, only gmac1 of an
40+ compatible string and the reg must be 1. So, for now, only gmac1 of a
4241 MediaTek SoC can benefit this. Banana Pi BPI-R2 suits this.
43- Check out example 5 for a similar configuration.
44-
45- - Port 5 can be wired to an external phy. Port 5 becomes a DSA slave.
46- Check out example 7 for a similar configuration.
47-
48- For multi-chip module MT7530:
49-
50- - Port 5 can be used as a CPU port.
51-
52- - PHY 0 or 4 of the switch can be muxed to connect to gmac1 of the SoC.
53- Usually used for connecting the wan port directly to the CPU to achieve 2
54- Gbps routing in total.
55-
56- The driver looks up the reg on the ethernet-phy node which the phy-handle
57- property refers to on the gmac node to mux the specified phy.
5842
5943 For the MT7621 SoCs, rgmii2 group must be claimed with rgmii2 function.
44+
6045 Check out example 5.
6146
62- - In case of an external phy wired to gmac1 of the SoC, port 5 must not be
63- enabled.
47+ - For the multi-chip module MT7530, in case of an external phy wired to
48+ gmac1 of the SoC, port 5 must not be enabled.
6449
6550 In case of muxing PHY 0 or 4, the external phy must not be enabled.
6651
6752 For the MT7621 SoCs, rgmii2 group must be claimed with rgmii2 function.
53+
6854 Check out example 6.
6955
70- - Port 5 can be muxed to an external phy. Port 5 becomes a DSA slave.
71- The external phy must be wired TX to TX to gmac1 of the SoC for this to
72- work. Ubiquiti EdgeRouter X SFP is wired this way.
56+ - Port 5 can be wired to an external phy. Port 5 becomes a DSA slave.
57+
58+ For the multi-chip module MT7530, the external phy must be wired TX to TX
59+ to gmac1 of the SoC for this to work. Ubiquiti EdgeRouter X SFP is wired
60+ this way.
7361
74- Muxing PHY 0 or 4 won't work when the external phy is connected TX to TX.
62+ For the multi-chip module MT7530, muxing PHY 0 or 4 won't work when the
63+ external phy is connected TX to TX.
7564
7665 For the MT7621 SoCs, rgmii2 group must be claimed with gpio function.
66+
7767 Check out example 7.
7868
7969properties :
@@ -601,7 +591,7 @@ examples:
601591 label = "lan4";
602592 };
603593
604- /* Commented out, phy4 is muxed to gmac1.
594+ /* Commented out, phy4 is connected to gmac1.
605595 port@4 {
606596 reg = <4>;
607597 label = "wan";
0 commit comments