From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Daniel Golle <daniel@makrotopia.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"sander@svanheule.net" <sander@svanheule.net>,
"markus.stockhausen@gmx.de" <markus.stockhausen@gmx.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v9] net: mdio: Add RTL9300 MDIO driver
Date: Mon, 10 Mar 2025 16:34:33 +0000 [thread overview]
Message-ID: <Z88Uma90VzLul2we@shell.armlinux.org.uk> (raw)
In-Reply-To: <b506b6e9-d5c3-4927-ab2d-e3a241513082@alliedtelesis.co.nz>
On Mon, Mar 10, 2025 at 02:07:26AM +0000, Chris Packham wrote:
> So far upstream Linux doesn't have generic paged PHY register functions.
> It sounds like that'd be a prerequisite for this.
If it doesn't, then what are:
phy_save_paged()
phy_select_page()
phy_restore_page()
phy_read_paged()
phy_write_paged()
phy_modify_paged()
etc?
These are at the _phy_ level because it requires the co-operation of
the PHY driver to select the page in the PHY (each PHY vendor does
paging differently.) They aren't a MDIO bus level thing because paging
doesn't exist at that level.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-03-10 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 23:25 [PATCH net-next v9] net: mdio: Add RTL9300 MDIO driver Chris Packham
2025-03-10 1:31 ` Daniel Golle
2025-03-10 2:07 ` Chris Packham
2025-03-10 15:28 ` Daniel Golle
2025-03-13 1:04 ` Chris Packham
2025-03-13 13:05 ` Andrew Lunn
2025-03-10 16:32 ` Andrew Lunn
2025-03-10 16:34 ` Russell King (Oracle) [this message]
2025-03-10 16:27 ` Andrew Lunn
2025-03-10 18:06 ` Christophe JAILLET
2025-03-10 18:15 ` Russell King (Oracle)
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=Z88Uma90VzLul2we@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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-kernel@vger.kernel.org \
--cc=markus.stockhausen@gmx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sander@svanheule.net \
/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.