diff options
| author | Arınç ÜNAL <arinc.unal@arinc9.com> | 2022-07-06 01:20:32 +0300 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2022-08-20 22:56:12 +0200 |
| commit | f1c9afd801380a05a91d979b475c76cc0a67caae (patch) | |
| tree | a6032afc3b214645a87cdb4f517901a433692fb9 /tools/xz | |
| parent | 81bd10e4a2f49f8351779a4b464d331f79f6a15c (diff) | |
| download | upstream-f1c9afd801380a05a91d979b475c76cc0a67caae.tar.gz upstream-f1c9afd801380a05a91d979b475c76cc0a67caae.tar.bz2 upstream-f1c9afd801380a05a91d979b475c76cc0a67caae.zip | |
ramips: mt7621-dts: mux phy0/4 to gmac1
Mux the MT7530 switch's phy0/4 to the SoC's gmac1 on devices where RGMII2
pins are available. This achieves 2 Gbps total bandwidth to the CPU using
the second RGMII.
The ports called "wan" are muxed where possible. On a minority of devices,
this is not possible. Those cases:
mt7621_ampedwireless_ally-r1900k.dts: lan3
mt7621_ubnt_edgerouter-x.dts: eth0
mt7621_gnubee_gb-pc1.dts: ethblue
mt7621_linksys_re6500.dts: lan1
mt7621_netgear_wac104.dts: lan4
mt7621_tplink_eap235-wall-v1.dts: lan0
mt7621_tplink_eap615-wall-v1.dts: lan0
mt7621_ubnt_usw-flex.dts: lan1
The "wan" port is just what the vendor designated on the board/plastic
chasis of the device. On a technical level, there is no difference between
a lan and wan port on MT7621AT, MT7621DAT and MT7621ST SoCs. Prefer
connecting to WAN via the port described above for these devices to benefit
the feature brought with this patch.
mt7621_d-team_newifi-d2.dts cannot benefit this feature, although it looks
like it should, because the rgmii2 pins are wired to unused components.
Tested on a range of devices documented on the GitHub PR.
Link: https://github.com/openwrt/openwrt/pull/10238
Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
Diffstat (limited to 'tools/xz')
0 files changed, 0 insertions, 0 deletions