[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <0e3ca573-2190-57b0-0e98-7f5b890d328e@arinc9.com>
Date: Thu, 15 Sep 2022 01:07:13 +0300
From: Arınç ÜNAL <arinc.unal@...nc9.com>
To: netdev <netdev@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Cc: Thibaut <hacks@...shdirt.org>, Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Sean Wang <sean.wang@...iatek.com>,
Landen Chao <Landen.Chao@...iatek.com>,
DENG Qingfang <dqfext@...il.com>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Sergio Paracuellos <sergio.paracuellos@...il.com>
Subject: Move MT7530 phy muxing from DSA to PHY driver
Hello folks.
MediaTek MT7530 switch has got 5 phys and 7 gmacs. gmac5 and gmac6 are
treated as CPU ports.
This switch has got a feature which phy0 or phy4 can be muxed to gmac5
of the switch. This allows an ethernet mac connected to gmac5 to
directly connect to the phy.
PHY muxing works by looking for the compatible string "mediatek,eth-mac"
then the mac address to find the gmac1 node. Then, it checks the mdio
address on the node which "phy-handle" on the gmac1 node points to. If
the mdio address is 0, phy0 is muxed to gmac5 of the switch. If it's 4,
phy4 is muxed.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/drivers/net/dsa/mt7530.c?id=1f9a6abecf538cc73635f6082677a2f4dc9c89a4#n2238
Because that DSA probes the switch before muxing the phy, this won't
work on devices which only use a single switch phy because probing will
fail.
I'd like this operation to be done from the MediaTek Gigabit PHY driver
instead. The motives for this change are that we solve the behaviour
above, liberate the need to use DSA for this operation and get rid of
the DSA overhead.
Would a change like this make sense and be accepted into netdev?
Arınç
Powered by blists - more mailing lists