[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7503a496e1456fa65e4317bbe7590d9d@walle.cc>
Date: Thu, 24 Mar 2022 15:28:43 +0100
From: Michael Walle <michael@...le.cc>
To: Andrew Lunn <andrew@...n.ch>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
"David S . Miller" <davem@...emloft.net>,
Xu Liang <lxu@...linear.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Florian Fainelli <f.fainelli@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC net-next 2/5] net: phy: support indirect c45 access in
get_phy_c45_ids()
Am 2022-03-23 20:39, schrieb Andrew Lunn:
>> +static int mdiobus_probe_mmd_read(struct mii_bus *bus, int prtad, int
>> devad,
>> + u16 regnum)
>> +{
>> + int ret;
>> +
>> + /* For backwards compatibility, treat MDIOBUS_NO_CAP as c45 capable
>> */
>> + if (bus->probe_capabilities == MDIOBUS_NO_CAP ||
>> + bus->probe_capabilities >= MDIOBUS_C45)
>
> Maybe we should do the work and mark up those that are C45 capable. At
> a quick count, see 16 of them.
I guess you grepped for MII_ADDR_C45 and had a look who
actually handled it correctly. Correct?
Let's say we mark these as either MDIOBUS_C45 or MDIOBUS_C45_C22,
can we then drop MDIOBUS_NO_CAP and make MDIOBUS_C22 the default
value (i.e. value 0) or do we have to go through all the mdio drivers
and add bus->probe_capabilities = MDIOBUS_C22 ? Grepping for
{of_,}mdiobus_register lists quite a few of them.
-michael
Powered by blists - more mailing lists