From: Daniel Walker <danielwa@cisco.com>
To: Claudiu Manoil <claudiu.manoil@nxp.com>
Cc: Hemant Ramdasi <hramdasi@cisco.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [danielwa@cisco.com: Re: gianfar: Implement MAC reset and reconfig procedure]
Date: Thu, 18 Oct 2018 10:11:50 -0700 [thread overview]
Message-ID: <20181018171150.mapmxugiew7f6x2g@zorba> (raw)
In-Reply-To: <HE1PR04MB1145DAA9F214275D6489B06B96F80@HE1PR04MB1145.eurprd04.prod.outlook.com>
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
next prev parent reply other threads:[~2018-10-19 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181017222944.yviao7l4xkndtgl3@zorba>
[not found] ` <HE1PR04MB114545F641D276841BA2656F96F80@HE1PR04MB1145.eurprd04.prod.outlook.com>
2018-10-18 13:42 ` [danielwa@cisco.com: Re: gianfar: Implement MAC reset and reconfig procedure] Daniel Walker
2018-10-18 14:05 ` Daniel Walker
2018-10-18 16:49 ` Claudiu Manoil
2018-10-18 17:11 ` Daniel Walker [this message]
2018-10-19 16:21 ` Daniel Walker
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=20181018171150.mapmxugiew7f6x2g@zorba \
--to=danielwa@cisco.com \
--cc=claudiu.manoil@nxp.com \
--cc=hramdasi@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).