From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: "'Andrew Lunn'" <andrew@lunn.ch>,
"'Daniel Golle'" <daniel@makrotopia.org>
Cc: <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<chris.packham@alliedtelesis.co.nz>
Subject: AW: [PATCH 3/9] net: mdio: realtek-rtl9300: Add ports to info structure
Date: Tue, 19 May 2026 21:06:30 +0200 [thread overview]
Message-ID: <01d801dce7c2$a0a08ba0$e1e1a2e0$@gmx.de> (raw)
In-Reply-To: <85d5f162-8999-43d4-b879-6e5e686246f7@lunn.ch>
Hi Andrew,
> Von: Andrew Lunn <andrew@lunn.ch>
> Gesendet: Dienstag, 19. Mai 2026 20:00
> An: Daniel Golle <daniel@makrotopia.org>
> Betreff: Re: [PATCH 3/9] net: mdio: realtek-rtl9300: Add ports to info
structure
>
> On Tue, May 19, 2026 at 06:27:55PM +0100, Daniel Golle wrote:
> > On Tue, May 19, 2026 at 06:57:41PM +0200, Markus Stockhausen wrote:
> > > Each Realtek SOC series has different number of MDIO ports.
> >
> > I don't think the term "MDIO ports" describes it well.
> >
> > I'd say "switch ports", also because RTL9300_NUM_PORTS includes ports
> > used for SFP+ cages which aren't going to be (directly) associated
> > with any MDIO-connected PHY at all.
>
> Hi Markus
>
> It would be good to take a step back and explain the concepts here in
> the commit message. An MDIO bus as 32 addresses, as defined by
> 802.3. Why do we need the concept of a port when we have addresses?
>
> Once you explain the concept, we can maybe suggest a better name. Or
> throw the whole concept out because it is not needed.
I'm just trying to give the properties in the info structure the right
name that resembles its function. The driver already builds upon
the "port" naming.
Where does this come from?
- The hardware has 1-4 SMI busses
- Each bus serves up to 32 addresses
- A switch has X physical ports
- The mdio controller can only be fed with "physical port"
To make this work:
- port->bus/address hardware mapping registers are set up. [1]
- Driver exposes bus/address to kernel as usual
- During access driver converts bus/address to port [2]
- Driver issues command towards hardware via port
- Hardware maps that back to bus/address
So basically the driver needs an "port-like-index" for all
its operations. Looking at the initial PR history [2] I assume
this design was already hard enough to implement.
Markus
[1]
https://elixir.bootlin.com/linux/v6.18.1/source/drivers/net/mdio/mdio-realte
k-rtl9300.c#L319
[2]
https://elixir.bootlin.com/linux/v6.18.1/source/drivers/net/mdio/mdio-realte
k-rtl9300.c#L66
[3] https://marc.info/?l=linux-netdev&w=2&r=3&s=add+rtl9300+mdio+driver&q=b
next prev parent reply other threads:[~2026-05-19 19:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 16:57 [PATCH 0/9] mdio: realtek-rtl9300: Groundwork for multi SOC support Markus Stockhausen
2026-05-19 16:57 ` [PATCH 1/9] net: mdio: realtek-rtl9300: Convert to generic prefix Markus Stockhausen
2026-05-19 17:51 ` Andrew Lunn
2026-05-19 16:57 ` [PATCH 2/9] net: mdio: realtek-rtl9300: Add device specific info structure Markus Stockhausen
2026-05-19 16:57 ` [PATCH 3/9] net: mdio: realtek-rtl9300: Add ports to " Markus Stockhausen
2026-05-19 17:27 ` Daniel Golle
2026-05-19 17:59 ` Andrew Lunn
2026-05-19 19:06 ` Markus Stockhausen [this message]
2026-05-19 20:14 ` Andrew Lunn
2026-05-19 20:36 ` AW: " Markus Stockhausen
2026-05-19 22:47 ` Daniel Golle
2026-05-20 1:09 ` Andrew Lunn
[not found] ` <10121615-6F47-2A48-825A-0AC1E0C0F0C1@hxcore.ol>
2026-05-20 1:42 ` Andrew Lunn
2026-05-20 2:59 ` Daniel Golle
2026-05-19 16:57 ` [PATCH 4/9] net: mdio: realtek-rtl9300: Add pages " Markus Stockhausen
2026-05-19 17:29 ` Daniel Golle
2026-05-19 18:07 ` Andrew Lunn
2026-05-19 16:57 ` [PATCH 5/9] net: mdio: realtek-rtl9300: Add register structure Markus Stockhausen
2026-05-19 16:57 ` [PATCH 6/9] net: mdio: realtek-rtl9300: Add command/C22 register Markus Stockhausen
2026-05-19 16:57 ` [PATCH 7/9] net: mdio: realtek-rtl9300: Add I/O register Markus Stockhausen
2026-05-19 16:57 ` [PATCH 8/9] net: mdio: realtek-rtl9300: Add mask register Markus Stockhausen
2026-05-19 18:43 ` Andrew Lunn
2026-05-19 16:57 ` [PATCH 9/9] net: mdio: realtek-rtl9300: Link I/O functions in info structure Markus Stockhausen
2026-05-19 18:46 ` Andrew Lunn
2026-05-19 19:25 ` AW: " Markus Stockhausen
2026-05-19 20:16 ` Andrew Lunn
2026-05-19 20:40 ` AW: " Markus Stockhausen
2026-05-20 2:04 ` [PATCH 0/9] mdio: realtek-rtl9300: Groundwork for multi SOC support Chris Packham
2026-05-20 6:06 ` AW: " Markus Stockhausen
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='01d801dce7c2$a0a08ba0$e1e1a2e0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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