From: "Benno Lossin" <lossin@kernel.org>
To: "Christian Marangi" <ansuelsmth@gmail.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Marek Behún" <kabel@kernel.org>,
"Andrei Botila" <andrei.botila@oss.nxp.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Sabrina Dubroca" <sd@queasysnail.net>,
"Michael Klein" <michael@fossekall.de>,
"Daniel Golle" <daniel@makrotopia.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Cc: "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Subject: Re: [net-next PATCH v12 1/6] net: phy: pass PHY driver to .match_phy_device OP
Date: Sun, 18 May 2025 15:30:50 +0200 [thread overview]
Message-ID: <D9ZBNJ6VL5XL.2TIH5QSOI8ABL@kernel.org> (raw)
In-Reply-To: <20250517201353.5137-2-ansuelsmth@gmail.com>
On Sat May 17, 2025 at 10:13 PM CEST, Christian Marangi wrote:
> Pass PHY driver pointer to .match_phy_device OP in addition to phydev.
> Having access to the PHY driver struct might be useful to check the
> PHY ID of the driver is being matched for in case the PHY ID scanned in
> the phydev is not consistent.
>
> A scenario for this is a PHY that change PHY ID after a firmware is
> loaded, in such case, the PHY ID stored in PHY device struct is not
> valid anymore and PHY will manually scan the ID in the match_phy_device
> function.
>
> Having the PHY driver info is also useful for those PHY driver that
> implement multiple simple .match_phy_device OP to match specific MMD PHY
> ID. With this extra info if the parsing logic is the same, the matching
> function can be generalized by using the phy_id in the PHY driver
> instead of hardcoding.
>
> Rust wrapper callback is updated to align to the new match_phy_device
> arguments.
>
> Suggested-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> drivers/net/phy/bcm87xx.c | 6 ++++--
> drivers/net/phy/icplus.c | 6 ++++--
> drivers/net/phy/marvell10g.c | 12 ++++++++----
> drivers/net/phy/micrel.c | 6 ++++--
> drivers/net/phy/nxp-c45-tja11xx.c | 12 ++++++++----
> drivers/net/phy/nxp-tja11xx.c | 6 ++++--
> drivers/net/phy/phy_device.c | 2 +-
> drivers/net/phy/realtek/realtek_main.c | 27 +++++++++++++++++---------
> drivers/net/phy/teranetics.c | 3 ++-
> include/linux/phy.h | 3 ++-
> rust/kernel/net/phy.rs | 1 +
> 11 files changed, 56 insertions(+), 28 deletions(-)
I haven't really looked at the C code, just the part that interfaces
with Rust, so:
Reviewed-by: Benno Lossin <lossin@kernel.org> # for Rust
---
Cheers,
Benno
next prev parent reply other threads:[~2025-05-18 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 20:13 [net-next PATCH v12 0/6] net: phy: Add support for new Aeonsemi PHYs Christian Marangi
2025-05-17 20:13 ` [net-next PATCH v12 1/6] net: phy: pass PHY driver to .match_phy_device OP Christian Marangi
2025-05-18 13:30 ` Benno Lossin [this message]
2025-05-19 6:09 ` FUJITA Tomonori
2025-05-17 20:13 ` [net-next PATCH v12 2/6] net: phy: bcm87xx: simplify " Christian Marangi
2025-05-17 20:13 ` [net-next PATCH v12 3/6] net: phy: nxp-c45-tja11xx: " Christian Marangi
2025-05-17 20:13 ` [net-next PATCH v12 4/6] net: phy: introduce genphy_match_phy_device() Christian Marangi
2025-05-17 20:13 ` [net-next PATCH v12 5/6] net: phy: Add support for Aeonsemi AS21xxx PHYs Christian Marangi
2025-05-17 20:13 ` [net-next PATCH v12 6/6] dt-bindings: net: Document support for Aeonsemi PHYs Christian Marangi
2025-05-22 3:30 ` [net-next PATCH v12 0/6] net: phy: Add support for new " patchwork-bot+netdevbpf
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=D9ZBNJ6VL5XL.2TIH5QSOI8ABL@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=andrei.botila@oss.nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor+dt@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=hkallweit1@gmail.com \
--cc=kabel@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@fossekall.de \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=tmgross@umich.edu \
/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;
as well as URLs for NNTP newsgroup(s).