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 v2 2/2] net: dsa: microchip: remove MICREL_NO_EEE workaround
Date: Tue, 7 Jan 2025 21:08:02 +0100 [thread overview]
Message-ID: <4bb28f98-7e2f-4413-9d5e-c8ad5498be03@gmail.com> (raw)
In-Reply-To: <Z3za4bKAJWh3HO9u@pengutronix.de>
On 07.01.2025 08:42, Oleksij Rempel wrote:
> On Mon, Jan 06, 2025 at 02:23:36PM +0100, Heiner Kallweit wrote:
>> The integrated PHY's on all these switch types have the same PHY ID.
>> So we can assume that the issue is related to the PHY type, not the
>> switch type. After having disabled EEE for this PHY type, we can remove
>> the workaround code here.
>>
>> Note: On the fast ethernet models listed here the integrated PHY has
>> PHY ID 0x00221550, which is handled by PHY driver
>> "Micrel KSZ87XX Switch". This PHY driver doesn't handle flag
>> MICREL_NO_EEE, therefore setting the flag for these models
>> results in a no-op.
>
> Yes, it feels like no one is using KSZ87XX switches with the kernel DSA
> driver.
>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> drivers/net/dsa/microchip/ksz_common.c | 25 -------------------------
>> include/linux/micrel_phy.h | 1 -
>> 2 files changed, 26 deletions(-)
>>
>> diff --git a/drivers/net/dsa/microchip/ksz_common.c b/drivers/net/dsa/microchip/ksz_common.c
>> index e3512e324..4871bb1fc 100644
>> --- a/drivers/net/dsa/microchip/ksz_common.c
>> +++ b/drivers/net/dsa/microchip/ksz_common.c
>> @@ -3008,31 +3008,6 @@ static u32 ksz_get_phy_flags(struct dsa_switch *ds, int port)
>> if (!port)
>> return MICREL_KSZ8_P1_ERRATA;
>> break;
>> - case KSZ8567_CHIP_ID:
>> - /* KSZ8567R Errata DS80000752C Module 4 */
>> - case KSZ8765_CHIP_ID:
>> - case KSZ8794_CHIP_ID:
>> - case KSZ8795_CHIP_ID:
>> - /* KSZ879x/KSZ877x/KSZ876x Errata DS80000687C Module 2 */
>> - case KSZ9477_CHIP_ID:
>> - /* KSZ9477S Errata DS80000754A Module 4 */
>> - case KSZ9567_CHIP_ID:
>> - /* KSZ9567S Errata DS80000756A Module 4 */
>> - case KSZ9896_CHIP_ID:
>> - /* KSZ9896C Errata DS80000757A Module 3 */
>> - case KSZ9897_CHIP_ID:
>> - case LAN9646_CHIP_ID:
>> - /* KSZ9897R Errata DS80000758C Module 4 */
>> - /* Energy Efficient Ethernet (EEE) feature select must be manually disabled
>> - * The EEE feature is enabled by default, but it is not fully
>> - * operational. It must be manually disabled through register
>> - * controls. If not disabled, the PHY ports can auto-negotiate
>> - * to enable EEE, and this feature can cause link drops when
>> - * linked to another device supporting EEE.
>> - *
>> - * The same item appears in the errata for all switches above.
>> - */
>
> I have two problems with current patch set:
> - dropped documentation, not all switches are officially broken, so
> keeping it documented is important.
> - not all KSZ9xxx based switches are officially broken. All 3 port
> switches are not broken but still match against the KSZ9477 PHY
> driver:
> KSZ8563_CHIP_ID - 0x00221631
> KSZ9563_CHIP_ID - 0x00221631
> KSZ9893_CHIP_ID - 0x00221631
>
OK, thanks for the clarification. Then we have to go another way.
> Best Regards,
> Oleksij
prev parent reply other threads:[~2025-01-07 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 13:20 [PATCH net-next v2 0/2] microchip/micrel switch: replace MICREL_NO_EEE workaround Heiner Kallweit
2025-01-06 13:22 ` [PATCH net-next v2 1/2] net: phy: micrel: disable EEE on KSZ9477-type PHY Heiner Kallweit
2025-01-06 13:23 ` [PATCH net-next v2 2/2] net: dsa: microchip: remove MICREL_NO_EEE workaround Heiner Kallweit
2025-01-06 18:36 ` Andrew Lunn
2025-01-07 7:42 ` Oleksij Rempel
2025-01-07 13:03 ` Andrew Lunn
2025-01-07 13:26 ` Oleksij Rempel
2025-01-07 20:08 ` Heiner Kallweit [this message]
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=4bb28f98-7e2f-4413-9d5e-c8ad5498be03@gmail.com \
--to=hkallweit1@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@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 \
/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).