From: Harini Katakam <harinik@xilinx.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: danielwa@cisco.com, Florian Fainelli <f.fainelli@gmail.com>,
afleming@freescale.com,
Harini Katakam <harini.katakam@xilinx.com>,
netdev@vger.kernel.org, hramdasi@cisco.com, jpitti@cisco.com,
gcasheek@cisco.com
Subject: Re: Marvell phy errata origins?
Date: Wed, 26 Sep 2018 11:12:47 +0530 [thread overview]
Message-ID: <CAFcVECKWf8JS7W2s2zRBU0txeaERF-zUHTcMcF9xqXtphObM5g@mail.gmail.com> (raw)
In-Reply-To: <CAFcVEC+PW1Vv5SdmzHbDe=gffJKY3tTXYdW1G8-kopsRTZ91FQ@mail.gmail.com>
Hi,
On Tue, Sep 25, 2018 at 11:00 PM Harini Katakam <harinik@xilinx.com> wrote:
>
> Hi Daniel,
>
> On Tue, Sep 25, 2018 at 9:10 PM Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > > 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.
> >
>
> Yes, we weren't using interrupts; we used phy poll.
>
> As I recall, the register and page combination was reserved and
> the access seemed to fail.
> It will be useful if we can the errata description or version details.
> I'll check if I can get any more information.
One of the PHY parts used was "88E1111-B2-bab1i000"
Regards,
Harini
next prev parent reply other threads:[~2018-09-26 11:54 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
2018-09-25 17:30 ` Harini Katakam
2018-09-26 5:42 ` Harini Katakam [this message]
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=CAFcVECKWf8JS7W2s2zRBU0txeaERF-zUHTcMcF9xqXtphObM5g@mail.gmail.com \
--to=harinik@xilinx.com \
--cc=afleming@freescale.com \
--cc=andrew@lunn.ch \
--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).