From: Heiner Kallweit <hkallweit1@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>, Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
Simon Horman <horms@kernel.org>,
Woojung Huh <woojung.huh@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Tim Harvey <tharvey@gateworks.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 1/2] net: phy: micrel: disable EEE on KSZ9477-type PHY
Date: Fri, 20 Dec 2024 19:02:50 +0100 [thread overview]
Message-ID: <c9b5858d-5356-4ae4-b492-9bdd95152fde@gmail.com> (raw)
In-Reply-To: <Z2WB7aOs0m4Kamfl@pengutronix.de>
On 20.12.2024 15:40, Oleksij Rempel wrote:
> On Fri, Dec 20, 2024 at 02:51:32PM +0100, Heiner Kallweit wrote:
>> On several supported switches the integrated PHY's have buggy EEE.
>> On the GBit-capable ones it's always the same type of PHY with PHY ID
>> 0x00221631. So we can simplify the erratum handling by simply clearing
>> phydev->supported_eee for this PHY type.
>>
>> Note: The KSZ9477 PHY driver also covers e.g. the internal PHY of
>> KSZ9563 (ID: 0x00221637), which is unaffected by the EEE issue.
>> Therefore check for the exact PHY ID.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> drivers/net/phy/micrel.c | 12 ++++++------
>> 1 file changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
>> index 3ef508840..ece6d026e 100644
>> --- a/drivers/net/phy/micrel.c
>> +++ b/drivers/net/phy/micrel.c
>> @@ -1522,6 +1522,12 @@ static int ksz9477_get_features(struct phy_device *phydev)
>> if (ret)
>> return ret;
>>
>> + /* See KSZ9477 Errata DS80000754C Module 4 */
>> + if (phydev->phy_id == PHY_ID_KSZ9477) {
>> + linkmode_zero(phydev->supported_eee);
>> + return 0;
>> + }
>
> Hm.. with this change, we won't be able to disable EEE. Zeroed
> supported_eee will avoid writing to the EEE advertisement register.
>
Indeed, genphy_c45_write_eee_adv() would become a no-op.
We have to do it differently.
next prev parent reply other threads:[~2024-12-20 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 13:50 [PATCH net-next 0/2] microchip/micrel switch: replace MICREL_NO_EEE workaround Heiner Kallweit
2024-12-20 13:51 ` [PATCH net-next 1/2] net: phy: micrel: disable EEE on KSZ9477-type PHY Heiner Kallweit
2024-12-20 14:40 ` Oleksij Rempel
2024-12-20 18:02 ` Heiner Kallweit [this message]
2024-12-20 13:53 ` [PATCH net-next 2/2] net: dsa: microchip: remove MICREL_NO_EEE workaround Heiner Kallweit
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=c9b5858d-5356-4ae4-b492-9bdd95152fde@gmail.com \
--to=hkallweit1@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=tharvey@gateworks.com \
--cc=woojung.huh@microchip.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).