From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: "'Chris Packham'" <Chris.Packham@alliedtelesis.co.nz>,
<andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<daniel@makrotopia.org>
Subject: AW: [PATCH 0/9] mdio: realtek-rtl9300: Groundwork for multi SOC support
Date: Wed, 20 May 2026 08:06:26 +0200 [thread overview]
Message-ID: <008201dce81e$ceeddbf0$6cc993d0$@gmx.de> (raw)
In-Reply-To: <31a47180-e0cc-4731-aca4-e5266aecb7a2@alliedtelesis.co.nz>
Hi Chris,
> Von: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
> Gesendet: Mittwoch, 20. Mai 2026 04:05
> Betreff: Re: [PATCH 0/9] mdio: realtek-rtl9300: Groundwork for multi SOC support
> ...
> I see the MDIO(BUS,ADDR) -> PORT is still causing confusion. It is one
> of the more annoying aspects of the hardware. The basic summary is the
> hardware wants to own the PHYs but Linux wants to know about them too.
Thanks fort he heavy lifting last year. As I was not involved I read through
all what happened. For me [1] sums it up nicely.
> The Realtek SDK bundles this all together with lots of tightly coupled
> code oriented around switch ports. Linux wants PHYs and MACs to exist
> separately (IMHO this is the correct thing to do). I don't know how the
> Realtek SDK would deal with exotic PHYs with specific requirements for
> host/line side settings or non-PHY devices like we have with some DSA
> switches, I suspect it wouldn't
This tight coupling will kick in with future series. To make upstream
somehow production usable we need a place to at least
- setup port polling for ports that are not PHY but SerDes driven [2]
- classify port types [3]
So we must allow that the driver internally works on ports. And if we are
ok with this I want to remind of another challenge [4] that needs to be
solved.
Markus
[1] https://marc.info/?l=linux-netdev&m=174468002008100&w=2
[2] https://github.com/openwrt/openwrt/blob/d2fabb974c57cc96c12f783f2197cc2639e1ed5a/target/linux/realtek/files-6.18/drivers/net/mdio/mdio-realtek-otto.c#L814
[3] https://github.com/openwrt/openwrt/blob/d2fabb974c57cc96c12f783f2197cc2639e1ed5a/target/linux/realtek/files-6.18/drivers/net/mdio/mdio-realtek-otto.c#L793
[4] https://marc.info/?l=linux-netdev&m=176905734406837&w=2
prev parent reply other threads:[~2026-05-20 6:06 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 ` AW: " Markus Stockhausen
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 ` Markus Stockhausen [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='008201dce81e$ceeddbf0$6cc993d0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--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 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.