From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Walker <danielwa@cisco.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Andy Fleming <afleming@freescale.com>,
Harini Katakam <harini.katakam@xilinx.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
HEMANT RAMDASI <hramdasi@cisco.com>,
"Julius Hemanth Pitti -X (jpitti - MONTA VISTA SOFTWARE INC at
Cisco)" <jpitti@cisco.com>,
"GokulChand Casheekar (gcasheek)" <gcasheek@cisco.com>
Subject: Re: Marvell phy errata origins?
Date: Tue, 25 Sep 2018 17:39:16 +0200 [thread overview]
Message-ID: <20180925153916.GD1676@lunn.ch> (raw)
In-Reply-To: <84bfdc12-800c-2f63-3eff-416cf560e18c@cisco.com>
> 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
next prev parent reply other threads:[~2018-09-25 21:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 13:16 Marvell phy errata origins? Daniel Walker
2017-04-18 14:04 ` Andrew Lunn
2017-04-18 14:18 ` Daniel Walker
2017-04-18 14:31 ` Harini Katakam
2017-04-18 14:35 ` Daniel Walker
2017-04-18 14:41 ` Harini Katakam
2017-04-18 14:56 ` Daniel Walker
2017-04-18 15:09 ` Harini Katakam
2017-05-09 13:58 ` Daniel Walker
2017-05-09 14:24 ` Andrew Lunn
2018-09-25 15:16 ` Daniel Walker
2018-09-25 15:34 ` Andrew Lunn
2018-09-25 15:39 ` Andrew Lunn [this message]
2018-09-25 17:30 ` Harini Katakam
2018-09-26 5:42 ` Harini Katakam
2018-09-26 15:35 ` Daniel Walker
2018-10-01 10:26 ` GokulChand Casheekar (gcasheek)
2018-10-04 7:27 ` GokulChand Casheekar (gcasheek)
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=20180925153916.GD1676@lunn.ch \
--to=andrew@lunn.ch \
--cc=afleming@freescale.com \
--cc=danielwa@cisco.com \
--cc=f.fainelli@gmail.com \
--cc=gcasheek@cisco.com \
--cc=harini.katakam@xilinx.com \
--cc=hramdasi@cisco.com \
--cc=jpitti@cisco.com \
--cc=netdev@vger.kernel.org \
/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).