From: Matthias Brugger <matthias.bgg@gmail.com>
To: David Miller <davem@davemloft.net>, landen.chao@mediatek.com
Cc: andrew@lunn.ch, frank-w@public-files.de, f.fainelli@gmail.com,
dqfext@gmail.com, devicetree@vger.kernel.org,
netdev@vger.kernel.org, sean.wang@mediatek.com,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
opensource@vdorst.com, robh+dt@kernel.org,
linux-mediatek@lists.infradead.org, p.zabel@pengutronix.de,
kuba@kernel.org, vivien.didelot@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next v5 0/6] net-next: dsa: mt7530: add support for MT7531
Date: Mon, 21 Sep 2020 12:10:45 +0200 [thread overview]
Message-ID: <c485e60e-21af-ffd3-856c-dbfd497cf6f0@gmail.com> (raw)
In-Reply-To: <20200914.163228.1898649357949030454.davem@davemloft.net>
On 15/09/2020 01:32, David Miller wrote:
> From: Landen Chao <landen.chao@mediatek.com>
> Date: Fri, 11 Sep 2020 21:48:50 +0800
>
>> This patch series adds support for MT7531.
>>
>> MT7531 is the next generation of MT7530 which could be found on Mediatek
>> router platforms such as MT7622 or MT7629.
>>
>> It is also a 7-ports switch with 5 giga embedded phys, 2 cpu ports, and
>> the same MAC logic of MT7530. Cpu port 6 only supports SGMII interface.
>> Cpu port 5 supports either RGMII or SGMII in different HW SKU, but cannot
>> be muxed to PHY of port 0/4 like mt7530. Due to support for SGMII
>> interface, pll, and pad setting are different from MT7530.
>>
>> MT7531 SGMII interface can be configured in following mode:
>> - 'SGMII AN mode' with in-band negotiation capability
>> which is compatible with PHY_INTERFACE_MODE_SGMII.
>> - 'SGMII force mode' without in-band negotiation
>> which is compatible with 10B/8B encoding of
>> PHY_INTERFACE_MODE_1000BASEX with fixed full-duplex and fixed pause.
>> - 2.5 times faster clocked 'SGMII force mode' without in-band negotiation
>> which is compatible with 10B/8B encoding of
>> PHY_INTERFACE_MODE_2500BASEX with fixed full-duplex and fixed pause.
> ...
>
> Series applied, thank you.
>
Regarding the DTS patches: Please coordinate with me the next time. I want to
prevent merge conflicts if both mine and your tree add patches to the files.
Thanks,
Matthias
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-21 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 13:48 [PATCH net-next v5 0/6] net-next: dsa: mt7530: add support for MT7531 Landen Chao
2020-09-11 13:48 ` [PATCH net-next v5 1/6] net: dsa: mt7530: Refine message in Kconfig Landen Chao
2020-09-11 13:48 ` [PATCH net-next v5 2/6] net: dsa: mt7530: Extend device data ready for adding a new hardware Landen Chao
2020-09-11 13:48 ` [PATCH net-next v5 3/6] dt-bindings: net: dsa: add new MT7531 binding to support MT7531 Landen Chao
2020-09-11 16:25 ` Florian Fainelli
2020-09-11 13:48 ` [PATCH net-next v5 4/6] net: dsa: mt7530: Add the support of MT7531 switch Landen Chao
2020-09-11 13:48 ` [PATCH net-next v5 5/6] arm64: dts: mt7622: add mt7531 dsa to mt7622-rfb1 board Landen Chao
2020-09-11 13:48 ` [PATCH net-next v5 6/6] arm64: dts: mt7622: add mt7531 dsa to bananapi-bpi-r64 board Landen Chao
2020-09-11 17:49 ` Aw: " Frank Wunderlich
2020-09-11 16:47 ` [PATCH net-next v5 0/6] net-next: dsa: mt7530: add support for MT7531 Vladimir Oltean
2020-09-14 23:32 ` David Miller
2020-09-21 10:10 ` Matthias Brugger [this message]
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=c485e60e-21af-ffd3-856c-dbfd497cf6f0@gmail.com \
--to=matthias.bgg@gmail.com \
--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=kuba@kernel.org \
--cc=landen.chao@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=opensource@vdorst.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@gmail.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;
as well as URLs for NNTP newsgroup(s).