From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jim Liu <jim.t90615@gmail.com>
Cc: JJLIU0@nuvoton.com, florian.fainelli@broadcom.com,
andrew@lunn.ch, hkallweit1@gmail.com, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
giulio.benetti+tekvox@benettiengineering.com,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org
Subject: Re: [v2,net] net: phy: broadcom: Correct BCM5221 PHY model detection failure
Date: Mon, 17 Mar 2025 10:24:27 +0000 [thread overview]
Message-ID: <Z9f4W86z90PgtkBc@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250317063452.3072784-1-JJLIU0@nuvoton.com>
On Mon, Mar 17, 2025 at 02:34:52PM +0800, Jim Liu wrote:
> Use "BRCM_PHY_MODEL" can be applied to the entire 5221 family of PHYs.
>
> Fixes: 3abbd0699b67 ("net: phy: broadcom: add support for BCM5221 phy")
> Signed-off-by: Jim Liu <jim.t90615@gmail.com>
Looking at BRCM_PHY_MODEL() and BRCM_PHY_REV(), I think there's more
issues with this driver. E.g.:
#define BRCM_PHY_MODEL(phydev) \
((phydev)->drv->phy_id & (phydev)->drv->phy_id_mask)
#define BRCM_PHY_REV(phydev) \
((phydev)->drv->phy_id & ~((phydev)->drv->phy_id_mask))
#define PHY_ID_BCM50610 0x0143bd60
#define PHY_ID_BCM50610M 0x0143bd70
if ((BRCM_PHY_MODEL(phydev) == PHY_ID_BCM50610 ||
BRCM_PHY_MODEL(phydev) == PHY_ID_BCM50610M) &&
BRCM_PHY_REV(phydev) >= 0x3) {
and from the PHY driver table:
.phy_id = PHY_ID_BCM50610,
.phy_id_mask = 0xfffffff0,
.phy_id = PHY_ID_BCM50610M,
.phy_id_mask = 0xfffffff0,
BRCM_PHY_REV() looks at _this_ .phy_id in the table, and tries to match
it against the revision field bits 0-3 being >= 3 - but as we can see,
this field is set to the defined value which has bits 0-3 always as
zero. So, this if() statement is always false.
So, BRCM_PHY_REV() should be:
#define BRCM_PHY_REV(phydev) \
((phydev)->phy_id & ~(phydev)->drv->phy_id_mask)
Next, I question why BRCM_PHY_MODEL() exists in the first place.
phydev->drv->phy_id is initialised to the defined value(s), and then
we end up doing:
(phydev->drv->phy_id & phydev->drv->phy_id_mask) ==
one-of-those-defined-values
which is pointless, because we know that what is in phydev->drv->phy_id
/is/ one-of-those-defined-values.
Therefore, I would suggest:
#define BRCM_PHY_MODEL(phydev) ((phydev)->drv->phy_id)
is entirely sufficient, and with such a simple definition, I question
the value of BRCM_PHY_MODEL() existing.
--
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-17 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 6:34 [v2,net] net: phy: broadcom: Correct BCM5221 PHY model detection failure Jim Liu
2025-03-17 10:24 ` Russell King (Oracle) [this message]
2025-03-17 13:18 ` Florian Fainelli
2025-03-17 13:29 ` Russell King (Oracle)
2025-03-18 3:15 ` Jim Liu
2025-03-24 16:57 ` Russell King (Oracle)
2025-03-24 16:48 ` Jakub Kicinski
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=Z9f4W86z90PgtkBc@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=JJLIU0@nuvoton.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=giulio.benetti+tekvox@benettiengineering.com \
--cc=hkallweit1@gmail.com \
--cc=jim.t90615@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).