From: arinc9.unal@gmail.com
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
"Frank Wunderlich" <frank-w@public-files.de>,
erkin.bozoglu@xeront.com, "Sean Wang" <sean.wang@mediatek.com>,
"DENG Qingfang" <dqfext@gmail.com>
Subject: [PATCH v2 4/5] arm: dts: mt7623: mux phy0 on Bananapi BPI-R2
Date: Wed, 1 Feb 2023 21:56:55 +0300 [thread overview]
Message-ID: <20230201185656.17164-5-arinc.unal@arinc9.com> (raw)
In-Reply-To: <20230201185656.17164-1-arinc.unal@arinc9.com>
From: Arınç ÜNAL <arinc.unal@arinc9.com>
Mux the MT7530 switch's phy0 to gmac5 which is wired to the SoC's gmac1.
This achieves 2 Gbps total bandwidth to the CPU using the second RGMII.
With this, the interface name to access phy0 changes from wan to eth1.
Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
---
arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
index dc9b4f99eb8b..64700253fd35 100644
--- a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
+++ b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
@@ -182,6 +182,12 @@ fixed-link {
};
};
+&gmac1 {
+ status = "okay";
+ phy-mode = "rgmii";
+ phy-handle = <ðphy0>;
+};
+
ð {
status = "okay";
@@ -189,6 +195,10 @@ mdio-bus {
#address-cells = <1>;
#size-cells = <0>;
+ ethphy0: ethernet-phy@0 {
+ reg = <0>;
+ };
+
switch@1f {
compatible = "mediatek,mt7530";
reg = <0x1f>;
@@ -200,11 +210,6 @@ ports {
#address-cells = <1>;
#size-cells = <0>;
- port@0 {
- reg = <0>;
- label = "wan";
- };
-
port@1 {
reg = <1>;
label = "lan0";
--
2.37.2
next prev parent reply other threads:[~2023-02-01 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 18:56 [PATCH v2 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and mux phy arinc9.unal
2023-02-01 18:56 ` [PATCH v2 1/5] arm: dts: mt7623: add gmacs to mt7623.dtsi arinc9.unal
2023-02-01 18:56 ` [PATCH v2 2/5] arm: dts: mt7623: add mt7530 switch to mt7623a.dtsi arinc9.unal
2023-02-01 18:56 ` [PATCH v2 3/5] arm: dts: mt7623: change mt7530 switch address arinc9.unal
2023-02-01 18:56 ` arinc9.unal [this message]
2023-02-03 15:36 ` [PATCH v2 4/5] arm: dts: mt7623: mux phy0 on Bananapi BPI-R2 Frank Wunderlich
2023-02-03 18:20 ` Arınç ÜNAL
2023-02-03 18:54 ` Frank Wunderlich
2023-02-04 10:27 ` Aw: " Frank Wunderlich
2023-02-04 11:43 ` Frank Wunderlich
2023-02-04 12:12 ` Arınç ÜNAL
2023-02-04 13:07 ` Aw: " Frank Wunderlich
2023-02-04 15:50 ` Arınç ÜNAL
2023-02-08 18:47 ` Arınç ÜNAL
2023-02-01 18:56 ` [PATCH v2 5/5] arm: dts: mt7623: enable flow control on port@6 arinc9.unal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230201185656.17164-5-arinc.unal@arinc9.com \
--to=arinc9.unal@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=dqfext@gmail.com \
--cc=erkin.bozoglu@xeront.com \
--cc=frank-w@public-files.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®