From: Rob Herring <robh@kernel.org> To: Landen Chao <landen.chao@mediatek.com> Cc: andrew@lunn.ch, f.fainelli@gmail.com, vivien.didelot@savoirfairelinux.com, matthias.bgg@gmail.com, mark.rutland@arm.com, devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, davem@davemloft.net, sean.wang@mediatek.com, opensource@vdorst.com, frank-w@public-files.de, dqfext@gmail.com Subject: Re: [PATCH net-next v2 4/7] dt-bindings: net: dsa: add new MT7531 binding to support MT7531 Date: Tue, 25 Aug 2020 13:43:06 -0600 [thread overview] Message-ID: <20200825194306.GA1160944@bogus> (raw) In-Reply-To: <1ec38b68deec6f1c23e1236d38035b1823ea2ebf.1597729692.git.landen.chao@mediatek.com> On Tue, Aug 18, 2020 at 03:14:09PM +0800, Landen Chao wrote: > Add devicetree binding to support the compatible mt7531 switch as used > in the MediaTek MT7531 switch. > > Signed-off-by: Sean Wang <sean.wang@mediatek.com> > Signed-off-by: Landen Chao <landen.chao@mediatek.com> > --- > .../devicetree/bindings/net/dsa/mt7530.txt | 71 ++++++++++++++++++- > 1 file changed, 68 insertions(+), 3 deletions(-) > > diff --git a/Documentation/devicetree/bindings/net/dsa/mt7530.txt b/Documentation/devicetree/bindings/net/dsa/mt7530.txt > index c5ed5d25f642..50eaf40fb612 100644 > --- a/Documentation/devicetree/bindings/net/dsa/mt7530.txt > +++ b/Documentation/devicetree/bindings/net/dsa/mt7530.txt > @@ -5,6 +5,7 @@ Required properties: > > - compatible: may be compatible = "mediatek,mt7530" > or compatible = "mediatek,mt7621" > + or compatible = "mediatek,mt7531" > - #address-cells: Must be 1. > - #size-cells: Must be 0. > - mediatek,mcm: Boolean; if defined, indicates that either MT7530 is the part > @@ -32,10 +33,13 @@ Required properties for the child nodes within ports container: > > - reg: Port address described must be 6 for CPU port and from 0 to 5 for > user ports. > -- phy-mode: String, must be either "trgmii" or "rgmii" for port labeled > - "cpu". > +- phy-mode: String, the follow value would be acceptable for port labeled "cpu" > + If compatible mediatek,mt7530 or mediatek,mt7621 is set, > + must be either "trgmii" or "rgmii" > + If compatible mediatek,mt7531 is set, > + must be either "sgmii", "1000base-x" or "2500base-x" > > -Port 5 of the switch is muxed between: > +Port 5 of mt7530 and mt7621 switch is muxed between: > 1. GMAC5: GMAC5 can interface with another external MAC or PHY. > 2. PHY of port 0 or port 4: PHY interfaces with an external MAC like 2nd GMAC > of the SOC. Used in many setups where port 0/4 becomes the WAN port. > @@ -308,3 +312,64 @@ Example 3: MT7621: Port 5 is connected to external PHY: Port 5 -> external PHY. > }; > }; > }; > + > +Example 4: MT7531BE port6 -- up-clocked 2.5Gbps SGMII -- MT7622 CPU 1st GMAC Does this really need another example? > + > +ð { > + gmac0: mac@0 { > + compatible = "mediatek,eth-mac"; > + reg = <0>; > + phy-mode = "2500base-x"; > + > + fixed-link { > + speed = <2500>; > + full-duplex; > + pause; > + }; > + }; > + > + &mdio0 { > + switch@0 { > + compatible = "mediatek,mt7531"; > + reg = <0>; > + reset-gpios = <&pio 54 0>; > + > + ports { > + #address-cells = <1>; > + #size-cells = <0>; > + reg = <0>; > + > + port@0 { > + reg = <0>; > + label = "lan0"; > + }; > + > + port@1 { > + reg = <1>; > + label = "lan1"; > + }; > + > + port@2 { > + reg = <2>; > + label = "lan2"; > + }; > + > + port@3 { > + reg = <3>; > + label = "lan3"; > + }; > + > + port@4 { > + reg = <4>; > + label = "wan"; > + }; > + > + port@6 { > + reg = <6>; > + label = "cpu"; > + ethernet = <&gmac0>; > + phy-mode = "2500base-x"; > + }; > + }; > + }; > + }; > -- > 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org> To: Landen Chao <landen.chao@mediatek.com> Cc: mark.rutland@arm.com, andrew@lunn.ch, frank-w@public-files.de, f.fainelli@gmail.com, dqfext@gmail.com, devicetree@vger.kernel.org, netdev@vger.kernel.org, vivien.didelot@savoirfairelinux.com, linux-kernel@vger.kernel.org, opensource@vdorst.com, linux-mediatek@lists.infradead.org, sean.wang@mediatek.com, matthias.bgg@gmail.com, davem@davemloft.net Subject: Re: [PATCH net-next v2 4/7] dt-bindings: net: dsa: add new MT7531 binding to support MT7531 Date: Tue, 25 Aug 2020 13:43:06 -0600 [thread overview] Message-ID: <20200825194306.GA1160944@bogus> (raw) In-Reply-To: <1ec38b68deec6f1c23e1236d38035b1823ea2ebf.1597729692.git.landen.chao@mediatek.com> On Tue, Aug 18, 2020 at 03:14:09PM +0800, Landen Chao wrote: > Add devicetree binding to support the compatible mt7531 switch as used > in the MediaTek MT7531 switch. > > Signed-off-by: Sean Wang <sean.wang@mediatek.com> > Signed-off-by: Landen Chao <landen.chao@mediatek.com> > --- > .../devicetree/bindings/net/dsa/mt7530.txt | 71 ++++++++++++++++++- > 1 file changed, 68 insertions(+), 3 deletions(-) > > diff --git a/Documentation/devicetree/bindings/net/dsa/mt7530.txt b/Documentation/devicetree/bindings/net/dsa/mt7530.txt > index c5ed5d25f642..50eaf40fb612 100644 > --- a/Documentation/devicetree/bindings/net/dsa/mt7530.txt > +++ b/Documentation/devicetree/bindings/net/dsa/mt7530.txt > @@ -5,6 +5,7 @@ Required properties: > > - compatible: may be compatible = "mediatek,mt7530" > or compatible = "mediatek,mt7621" > + or compatible = "mediatek,mt7531" > - #address-cells: Must be 1. > - #size-cells: Must be 0. > - mediatek,mcm: Boolean; if defined, indicates that either MT7530 is the part > @@ -32,10 +33,13 @@ Required properties for the child nodes within ports container: > > - reg: Port address described must be 6 for CPU port and from 0 to 5 for > user ports. > -- phy-mode: String, must be either "trgmii" or "rgmii" for port labeled > - "cpu". > +- phy-mode: String, the follow value would be acceptable for port labeled "cpu" > + If compatible mediatek,mt7530 or mediatek,mt7621 is set, > + must be either "trgmii" or "rgmii" > + If compatible mediatek,mt7531 is set, > + must be either "sgmii", "1000base-x" or "2500base-x" > > -Port 5 of the switch is muxed between: > +Port 5 of mt7530 and mt7621 switch is muxed between: > 1. GMAC5: GMAC5 can interface with another external MAC or PHY. > 2. PHY of port 0 or port 4: PHY interfaces with an external MAC like 2nd GMAC > of the SOC. Used in many setups where port 0/4 becomes the WAN port. > @@ -308,3 +312,64 @@ Example 3: MT7621: Port 5 is connected to external PHY: Port 5 -> external PHY. > }; > }; > }; > + > +Example 4: MT7531BE port6 -- up-clocked 2.5Gbps SGMII -- MT7622 CPU 1st GMAC Does this really need another example? > + > +ð { > + gmac0: mac@0 { > + compatible = "mediatek,eth-mac"; > + reg = <0>; > + phy-mode = "2500base-x"; > + > + fixed-link { > + speed = <2500>; > + full-duplex; > + pause; > + }; > + }; > + > + &mdio0 { > + switch@0 { > + compatible = "mediatek,mt7531"; > + reg = <0>; > + reset-gpios = <&pio 54 0>; > + > + ports { > + #address-cells = <1>; > + #size-cells = <0>; > + reg = <0>; > + > + port@0 { > + reg = <0>; > + label = "lan0"; > + }; > + > + port@1 { > + reg = <1>; > + label = "lan1"; > + }; > + > + port@2 { > + reg = <2>; > + label = "lan2"; > + }; > + > + port@3 { > + reg = <3>; > + label = "lan3"; > + }; > + > + port@4 { > + reg = <4>; > + label = "wan"; > + }; > + > + port@6 { > + reg = <6>; > + label = "cpu"; > + ethernet = <&gmac0>; > + phy-mode = "2500base-x"; > + }; > + }; > + }; > + }; > -- > 2.17.1 _______________________________________________ Linux-mediatek mailing list Linux-mediatek@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-08-25 19:43 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-18 7:14 [PATCH net-next v2 0/7] net-next: dsa: mt7530: add support for MT7531 Landen Chao 2020-08-18 7:14 ` Landen Chao 2020-08-18 7:14 ` [PATCH net-next v2 1/7] net: dsa: mt7530: Refine message in Kconfig Landen Chao 2020-08-18 7:14 ` Landen Chao 2020-08-18 7:14 ` [PATCH net-next v2 2/7] net: dsa: mt7530: support full-duplex gigabit only Landen Chao 2020-08-18 7:14 ` Landen Chao 2020-08-18 15:49 ` Andrew Lunn 2020-08-18 15:49 ` Andrew Lunn 2020-08-18 7:14 ` [PATCH net-next v2 3/7] net: dsa: mt7530: Extend device data ready for adding a new hardware Landen Chao 2020-08-18 7:14 ` Landen Chao 2020-08-18 15:56 ` Andrew Lunn 2020-08-18 15:56 ` Andrew Lunn 2020-08-18 17:31 ` Frank Wunderlich 2020-08-18 17:31 ` Frank Wunderlich 2020-08-18 7:14 ` [PATCH net-next v2 4/7] dt-bindings: net: dsa: add new MT7531 binding to support MT7531 Landen Chao 2020-08-18 7:14 ` Landen Chao 2020-08-25 19:43 ` Rob Herring [this message] 2020-08-25 19:43 ` Rob Herring 2020-08-18 7:14 ` [PATCH net-next v2 5/7] net: dsa: mt7530: Add the support of MT7531 switch Landen Chao 2020-08-18 7:14 ` Landen Chao 2020-08-18 15:23 ` Jakub Kicinski 2020-08-18 15:23 ` Jakub Kicinski 2020-08-19 9:50 ` Landen Chao 2020-08-19 9:50 ` Landen Chao 2020-08-18 16:09 ` Andrew Lunn 2020-08-18 16:09 ` Andrew Lunn 2020-08-19 9:44 ` Landen Chao 2020-08-19 9:44 ` Landen Chao 2020-08-19 13:12 ` Andrew Lunn 2020-08-19 13:12 ` Andrew Lunn 2020-08-19 23:46 ` René van Dorst 2020-08-19 23:46 ` René van Dorst 2020-08-20 15:29 ` Chuanhong Guo 2020-08-20 15:29 ` Chuanhong Guo 2020-08-18 7:14 ` [PATCH net-next v2 6/7] arm64: dts: mt7622: add mt7531 dsa to mt7622-rfb1 board Landen Chao 2020-08-18 7:14 ` Landen Chao 2020-08-18 16:10 ` Andrew Lunn 2020-08-18 16:10 ` Andrew Lunn 2020-08-18 7:14 ` [PATCH net-next v2 7/7] arm64: dts: mt7622: add mt7531 dsa to bananapi-bpi-r64 board Landen Chao 2020-08-18 7:14 ` Landen Chao 2020-08-18 16:24 ` Vladimir Oltean 2020-08-18 16:24 ` Vladimir Oltean 2020-08-19 8:15 ` Landen Chao 2020-08-19 8:15 ` Landen Chao 2020-08-19 8:51 ` Vladimir Oltean 2020-08-19 8:51 ` Vladimir Oltean 2020-08-18 17:54 ` Aw: [PATCH net-next v2 0/7] net-next: dsa: mt7530: add support for MT7531 Frank Wunderlich 2020-08-18 17:54 ` Frank Wunderlich 2020-08-19 3:49 ` DENG Qingfang 2020-08-19 3:49 ` DENG Qingfang 2020-08-19 6:57 ` Frank Wunderlich 2020-08-19 7:38 ` Landen Chao 2020-08-19 7:38 ` Landen Chao
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=20200825194306.GA1160944@bogus \ --to=robh@kernel.org \ --cc=andrew@lunn.ch \ --cc=davem@davemloft.net \ --cc=devicetree@vger.kernel.org \ --cc=dqfext@gmail.com \ --cc=f.fainelli@gmail.com \ --cc=frank-w@public-files.de \ --cc=landen.chao@mediatek.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=mark.rutland@arm.com \ --cc=matthias.bgg@gmail.com \ --cc=netdev@vger.kernel.org \ --cc=opensource@vdorst.com \ --cc=sean.wang@mediatek.com \ --cc=vivien.didelot@savoirfairelinux.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.