From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonas Jelonek <jelonek.jonas@gmail.com>,
Markus Stockhausen <markus.stockhausen@gmx.de>
Subject: Re: [PATCH RFC net-next] net: phy: add (*register_phy)() hook to struct mii_bus
Date: Wed, 21 Jan 2026 22:18:39 +0100 [thread overview]
Message-ID: <ef74e8c8-01c9-4ebe-911e-54e84eecb6f5@lunn.ch> (raw)
In-Reply-To: <34ac2837b01f53ace02c613a57a03a74d9a056b0.1769029647.git.daniel@makrotopia.org>
On Wed, Jan 21, 2026 at 09:12:56PM +0000, Daniel Golle wrote:
> Some MDIO busses require to program PHY polling registers depending on
> the PHY type. RealTek switch SoCs are the most prominent example of a
> DSA switch which doesn't allow to program MAC speed, duplex and
> flow-control settings without using PHY polling to do so.
>
> Hence there is a need to inform the MDIO bus driver that a PHY has been
> registered on the bus, as otherwise the bus driver will have to reinvent
> and duplicate all the bus scanning logic for Clause-22 and Clause-45
> PHYs.
>
> Provide a simple hook in struct mii_bus which is called right after a
> PHY has been registered on the bus.
>
> Alternative ways which would allow to do the same things without
> having to change any kernel code would of course be very welcome.
You need to provide a user of this new API as part of the patchset. To
deciding if an API makes sense you often need to see both sides of it.
Andrew
---
pw-bot: cr
prev parent reply other threads:[~2026-01-21 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 21:12 Daniel Golle
2026-01-21 21:18 ` Andrew Lunn [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=ef74e8c8-01c9-4ebe-911e-54e84eecb6f5@lunn.ch \
--to=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jelonek.jonas@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=markus.stockhausen@gmx.de \
--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
all inboxes | Powered by JetHome®