[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181018171150.mapmxugiew7f6x2g@zorba>
Date: Thu, 18 Oct 2018 10:11:50 -0700
From: Daniel Walker <danielwa@...co.com>
To: Claudiu Manoil <claudiu.manoil@....com>
Cc: Hemant Ramdasi <hramdasi@...co.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [danielwa@...co.com: Re: gianfar: Implement MAC reset and
reconfig procedure]
On Thu, Oct 18, 2018 at 04:49:26PM +0000, Claudiu Manoil wrote:
> I can only advise you to check whether the MACCFG2 register settings are consistent
> at this point, when ping fails. You should check the I/F Mode bits (22-23) and the
> Full Duplex bit (31), in big-endian format. If these do not match the 100Mbps full
> duplex link mode, then it might be that another thread (probably doing reset_gfar)
> changes MACCFG2 concurrently. I think MACCFG2 may be dumped with ethtool -d.
> I can get my hands on a board no sooner than maybe next week.
A board won't help you .. I'm running on customer hardware which you don't have
access to.
After boot up you have MACCFG2 = 0x7205 which is the same
as the INIT settings.
After the interface is brought up adjust_link() changes to MACCFG2 = 0x7105
which I think is MII.
0x7105 stays after the interface is brought down until gfar_mac_reset sets it to
0x7205 (GMII) .. then adjust link resets it to 0x7105 (MII) ..
That goes on and on each time to interface is brought down/up. It seems like
this is what your expecting to happen, but it doesn't seems to work %100 of the
time.
Daniel
Powered by blists - more mailing lists