[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180925153916.GD1676@lunn.ch>
Date: Tue, 25 Sep 2018 17:39:16 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Daniel Walker <danielwa@...co.com>
Cc: Florian Fainelli <f.fainelli@...il.com>,
Andy Fleming <afleming@...escale.com>,
Harini Katakam <harini.katakam@...inx.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
HEMANT RAMDASI <hramdasi@...co.com>,
"Julius Hemanth Pitti -X (jpitti - MONTA VISTA SOFTWARE INC at Cisco)"
<jpitti@...co.com>,
"GokulChand Casheekar (gcasheek)" <gcasheek@...co.com>
Subject: Re: Marvell phy errata origins?
> I hope this this thread isn't too old to bring back to life. So it seems
> that Harini found that m88e1111 did not need this errata, and Cisco
> previously found that Harini's patch fixed m88e1112, we included it
> internally for that reason
>
> Now I'm getting reports that this errata fixes issues we're seeing on
> m88e1111. We see an interrupt storm without the errata, despite the errata
> not being defined in the datasheet.
Is everybody actually using interrupts? It could be in one system
phylib is polling.
When you get an interrupt storm, which interrupt bit is not cleared by
reading the ievent register?
Andrew
Powered by blists - more mailing lists