From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: <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>,
<chris.packham@alliedtelesis.co.nz>, <daniel@makrotopia.org>
Subject: AW: [PATCH net-next v4 0/8] net: mdio: realtek-rtl9300: Add RTL83xx support
Date: Tue, 21 Jul 2026 17:17:07 +0200 [thread overview]
Message-ID: <05d501dd1924$00ac6cc0$02054640$@gmx.de> (raw)
In-Reply-To: <20260709064157.2865063-1-markus.stockhausen@gmx.de>
> Von: Markus Stockhausen <markus.stockhausen@gmx.de>
> Gesendet: Donnerstag, 9. Juli 2026 08:42
> Betreff: [PATCH net-next v4 0/8] net: mdio: realtek-rtl9300: Add RTL83xx
support
>
> The Realtek Otto switch platform consists of four different series
>
> - RTL838x aka maple : 28 port 1G Switches
> - RTL839x aka cypress : 52 port 1G Switches
> - RTL930x aka longan : 28 port 1G/2.5G/10G Switches
> - RTL931x aka mango : 56 port 1G/2.5G/10G Switches
>
> While the MDIO hardware polling unit and its necessity for the MAC
> layer was always well known, no detailed documentation was available.
> For this series the MDIO bus was inspected with a logic analyzer for
> a better understanding how polling and kernel access interact on the
> bus. All this will be explained now in the driver comments.
>
> This patch series adds support for the RTL83xx devices. For this
>
> - Enhance device tree binding.
> - Add special handling for limitations enforced by hardware polling.
> These already have minor side effects on RTL93xx devices but are even
> more critical for the RTL83xx hardware.
> - Add RTL83xx coding.
>
> Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
Gentle ping.
prev parent reply other threads:[~2026-07-21 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 6:41 [PATCH net-next v4 0/8] net: mdio: realtek-rtl9300: Add RTL83xx support Markus Stockhausen
2026-07-09 6:41 ` [PATCH net-next v4 1/8] dt-bindings: net: realtek,rtl9301-mdio: Add RTL83xx series Markus Stockhausen
2026-07-09 6:41 ` [PATCH net-next v4 2/8] net: mdio: realtek-rtl9300: Add polling documentation Markus Stockhausen
2026-07-09 6:41 ` [PATCH net-next v4 3/8] net: phy: add (*notify_phy_attach/detach)() hooks to struct mii_bus Markus Stockhausen
2026-07-21 18:15 ` Jakub Kicinski
2026-07-21 19:59 ` AW: " Markus Stockhausen
2026-07-21 20:45 ` Jakub Kicinski
2026-07-09 6:41 ` [PATCH net-next v4 4/8] net: mdio: realtek-rtl9300: Configure hardware polling during probing Markus Stockhausen
2026-07-09 6:41 ` [PATCH net-next v4 5/8] net: mdio: realtek-rtl9300: Add page tracking Markus Stockhausen
2026-07-09 6:41 ` [PATCH net-next v4 6/8] net: mdio: realtek-rtl9300: Increase MDIO timeout Markus Stockhausen
2026-07-09 6:41 ` [PATCH net-next v4 7/8] net: mdio: realtek-rtl9300: Add support for RTL838x Markus Stockhausen
2026-07-09 6:41 ` [PATCH net-next v4 8/8] net: mdio: realtek-rtl9300: Add support for RTL839x Markus Stockhausen
2026-07-21 15:17 ` 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='05d501dd1924$00ac6cc0$02054640$@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