[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFcVECKWf8JS7W2s2zRBU0txeaERF-zUHTcMcF9xqXtphObM5g@mail.gmail.com>
Date: Wed, 26 Sep 2018 11:12:47 +0530
From: Harini Katakam <harinik@...inx.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: danielwa@...co.com, Florian Fainelli <f.fainelli@...il.com>,
afleming@...escale.com, Harini Katakam <harini.katakam@...inx.com>,
netdev@...r.kernel.org, hramdasi@...co.com, jpitti@...co.com,
gcasheek@...co.com
Subject: Re: Marvell phy errata origins?
Hi,
On Tue, Sep 25, 2018 at 11:00 PM Harini Katakam <harinik@...inx.com> wrote:
>
> Hi Daniel,
>
> On Tue, Sep 25, 2018 at 9:10 PM Andrew Lunn <andrew@...n.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
Powered by blists - more mailing lists