From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: "'Andrew Lunn'" <andrew@lunn.ch>
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>, <daniel@makrotopia.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>
Subject: AW: [PATCH net-next v2 2/8] net: mdio: realtek-rtl9300: Add page tracking
Date: Mon, 29 Jun 2026 19:25:52 +0200 [thread overview]
Message-ID: <004201dd07ec$585a6ba0$090f42e0$@gmx.de> (raw)
In-Reply-To: <f3b0ddab-372a-49c5-977e-59c7a104d0a8@lunn.ch>
> Von: Andrew Lunn <andrew@lunn.ch>
> Gesendet: Montag, 29. Juni 2026 18:29
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Betreff: Re: [PATCH net-next v2 2/8] net: mdio: realtek-rtl9300: Add page
tracking
> ...
> > Intercept access to register 31 and store the desired value for each
port
> > in the driver. When issuing access to other registers add the saved
page.
> > This given, the hardware will run two consecutive c22 commands that are
> > not interrupted by polling.
> >
> > ... hardware poll ...
> > phy_write(phy, 31, page)
> > phy_write(phy, reg, value)
> > ... hardware poll ...
>
> How do you guarantee the polling will not get between?
The page is part of a single command towards the controller.
If a page is given the hardware will make the above two MDIO
commands out of this without any polling in between.
I will clarify this in the next version.
Markus
next prev parent reply other threads:[~2026-06-29 17:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 15:23 [PATCH net-next v2 0/8] net: mdio: realtek-rtl9300: Add RTL83xx support Markus Stockhausen
2026-06-29 15:23 ` [PATCH net-next v2 1/8] net: mdio: realtek-rtl9300: Add polling documentation Markus Stockhausen
2026-06-29 16:21 ` Andrew Lunn
2026-06-29 15:23 ` [PATCH net-next v2 2/8] net: mdio: realtek-rtl9300: Add page tracking Markus Stockhausen
2026-06-29 16:28 ` Andrew Lunn
2026-06-29 17:25 ` Markus Stockhausen [this message]
2026-06-29 15:23 ` [PATCH net-next v2 3/8] net: phy: add (*notify_phy_attach/detach)() hooks to struct mii_bus Markus Stockhausen
2026-06-30 15:24 ` sashiko-bot
2026-06-29 15:23 ` [PATCH net-next v2 4/8] net: mdio: realtek-rtl9300: Configure hardware polling during probing Markus Stockhausen
2026-06-29 16:38 ` Andrew Lunn
2026-07-03 2:24 ` Chris Packham
2026-06-30 15:24 ` sashiko-bot
2026-06-29 15:23 ` [PATCH net-next v2 5/8] net: mdio: realtek-rtl9300: Add c45 over c22 mitigation Markus Stockhausen
2026-06-29 16:40 ` Andrew Lunn
2026-06-29 17:29 ` AW: " Markus Stockhausen
2026-06-29 15:23 ` [PATCH net-next v2 6/8] net: mdio: realtek-rtl9300: Increase MDIO timeout Markus Stockhausen
2026-06-29 15:23 ` [PATCH net-next v2 7/8] net: mdio: realtek-rtl9300: Add support for RTL838x Markus Stockhausen
2026-06-29 15:23 ` [PATCH net-next v2 8/8] net: mdio: realtek-rtl9300: Add support for RTL839x 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='004201dd07ec$585a6ba0$090f42e0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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.