From: Andrew Lunn <andrew@lunn.ch>
To: Thangaraj.S@microchip.com
Cc: netdev@vger.kernel.org, fiona.klute@gmx.de,
andrew+netdev@lunn.ch, linux-usb@vger.kernel.org,
davem@davemloft.net, Rengarajan.S@microchip.com,
kernel-list@raspberrypi.com, linux-kernel@vger.kernel.org,
kuba@kernel.org, pabeni@redhat.com, edumazet@google.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net v2] net: phy: microchip: force IRQ polling mode for lan88xx
Date: Thu, 17 Apr 2025 20:11:00 +0200 [thread overview]
Message-ID: <3c6abdaf-b4e4-440f-9d75-745741287007@lunn.ch> (raw)
In-Reply-To: <ebb1fe9a31abc4045b2f95072c6d3d94ee83239e.camel@microchip.com>
On Thu, Apr 17, 2025 at 02:17:20PM +0000, Thangaraj.S@microchip.com wrote:
> Hi Flona,
> We haven't observed this issue with our LAN7801 + LAN88xx setup during
> testing in our setups. Issue reported specifically in RPI and NVidea
> with which we have not tested recently. Additionally, community
> discussions suggest that this issue may have been introduced due to
> driver updates in the LAN78xx. There's no hardware errata indicating
> any problems with the interrupts in LAN88xx.
>
> If the issue lies in the interrupt handling within the LAN78xx, it's
> likely that similar problems could arise with other PHYs that support
> interrupt handling. This need to be debugged and addressed from LAN78xx
> driver rather than removing interrupt support in LAN88xx.
Hi Thangaraj
It is an easily available platform. Maybe you can get one and try to
debug it?
This is a self contained simple fix. From a pragmatic standpoint, it
solves an issue which is bothering people. If you do find and fix an
issue in the LAN78xx this change can be easily reverted. So i'm
learning towards merging it.
Andrew
next prev parent reply other threads:[~2025-04-17 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 10:24 [PATCH net v2] net: phy: microchip: force IRQ polling mode for lan88xx Fiona Klute
2025-04-16 12:27 ` Andrew Lunn
2025-04-17 9:05 ` Fiona Klute
2025-04-17 14:17 ` Thangaraj.S
2025-04-17 18:11 ` Andrew Lunn [this message]
2025-04-21 4:17 ` Thangaraj.S
2025-04-22 10:51 ` Paolo Abeni
2025-04-22 11:10 ` patchwork-bot+netdevbpf
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=3c6abdaf-b4e4-440f-9d75-745741287007@lunn.ch \
--to=andrew@lunn.ch \
--cc=Rengarajan.S@microchip.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fiona.klute@gmx.de \
--cc=kernel-list@raspberrypi.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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