From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: "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>,
"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>,
"Sabrina Dubroca" <sd@queasysnail.net>,
"Daniel Golle" <daniel@makrotopia.org>,
"Eric Woudstra" <ericwouds@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next RFC PATCH v4 3/6] net: phy: nxp-c45-tja11xx: simplify .match_phy_device OP
Date: Fri, 28 Mar 2025 08:31:02 +0000 [thread overview]
Message-ID: <Z-ZeRhR73FS4iOzz@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250327224529.814-4-ansuelsmth@gmail.com>
On Thu, Mar 27, 2025 at 11:45:14PM +0100, Christian Marangi wrote:
> Simplify .match_phy_device OP by using a generic function and using the
> new phy_id PHY driver info instead of hardcoding the matching PHY ID
> with new variant for macsec and no_macsec PHYs.
>
> Also make use of PHY_ID_MATCH_MODEL macro and drop PHY_ID_MASK define to
> introduce phy_id and phy_id_mask again in phy_driver struct.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> drivers/net/phy/nxp-c45-tja11xx.c | 39 +++++++++++--------------------
> 1 file changed, 14 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/net/phy/nxp-c45-tja11xx.c b/drivers/net/phy/nxp-c45-tja11xx.c
> index bc2b7cc0cebe..fccfc1468698 100644
> --- a/drivers/net/phy/nxp-c45-tja11xx.c
> +++ b/drivers/net/phy/nxp-c45-tja11xx.c
> @@ -19,7 +19,6 @@
>
> #include "nxp-c45-tja11xx.h"
>
> -#define PHY_ID_MASK GENMASK(31, 4)
> /* Same id: TJA1103, TJA1104 */
> #define PHY_ID_TJA_1103 0x001BB010
> /* Same id: TJA1120, TJA1121 */
> @@ -1971,31 +1970,17 @@ static int nxp_c45_macsec_ability(struct phy_device *phydev)
> return macsec_ability;
> }
>
> -static int tja1103_match_phy_device(struct phy_device *phydev,
> - const struct phy_driver *phydrv)
> +static int tja11xx_no_macsec_match_phy_device(struct phy_device *phydev,
> + const struct phy_driver *phydrv)
> {
> - return phy_id_compare(phydev->phy_id, PHY_ID_TJA_1103, PHY_ID_MASK) &&
> + return phy_id_compare(phydev->phy_id, phydrv->phy_id, phydrv->phy_id_mask) &&
We try to keep to less than 80 columns in networking, and this driver
does so, so please keep it that way.
(Note: the 80 column limit doesn't apply to printing messages, which
should not be line-wrapped to allow them to be searched for).
Other than that, thanks for addressing the other driver I pointed out
that benefits from this.
--
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-28 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 22:45 [net-next RFC PATCH v4 0/6] net: phy: Add support for new Aeonsemi PHYs Christian Marangi
2025-03-27 22:45 ` [net-next RFC PATCH v4 1/6] net: phy: pass PHY driver to .match_phy_device OP Christian Marangi
2025-03-28 8:24 ` Russell King (Oracle)
2025-03-28 8:29 ` Christian Marangi
2025-03-27 22:45 ` [net-next RFC PATCH v4 2/6] net: phy: bcm87xx: simplify " Christian Marangi
2025-03-27 22:45 ` [net-next RFC PATCH v4 3/6] net: phy: nxp-c45-tja11xx: " Christian Marangi
2025-03-28 8:31 ` Russell King (Oracle) [this message]
2025-03-27 22:45 ` [net-next RFC PATCH v4 4/6] net: phy: introduce genphy_match_phy_device() Christian Marangi
2025-03-27 22:45 ` [net-next RFC PATCH v4 5/6] net: phy: Add support for Aeonsemi AS21xxx PHYs Christian Marangi
2025-03-27 22:45 ` [net-next RFC PATCH v4 6/6] dt-bindings: net: Document support for Aeonsemi PHYs Christian Marangi
2025-03-31 20:40 ` Rob Herring
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=Z-ZeRhR73FS4iOzz@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrei.botila@oss.nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=ericwouds@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=kabel@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sd@queasysnail.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 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).