From: Mason <slash.tmp@free.fr>
To: netdev <netdev@vger.kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Mans Rullgard <mans@mansr.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Timur Tabi <timur@codeaurora.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Zefir Kurtisi <zefir.kurtisi@neratec.com>,
Martin Blumenstingl <martin.blumenstingl@gmail.com>,
Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>,
Daniel Mack <zonque@gmail.com>,
Sebastian Frias <sf84@laposte.net>
Subject: Re: Ethernet not working on a different SoC with same eth HW
Date: Fri, 4 Nov 2016 14:01:05 +0100 [thread overview]
Message-ID: <581C8691.2060306@free.fr> (raw)
In-Reply-To: <58177128.8090403@free.fr>
On 31/10/2016 17:28, Mason wrote:
> On 31/10/2016 16:53, Andrew Lunn wrote:
>
>>> I'll add a log for the request_irq call.
>>
>> And take a look at /proc/interrupts
>
> You're right, there does seem to be something wrong with the interrupts.
Having fixed that, I'm still unable to ping a box on the same
ethernet segment... Still investigating.
I think I may have spotted a potential issue in the Atheros driver.
if (phydev->interface == PHY_INTERFACE_MODE_RGMII_RXID ||
phydev->interface == PHY_INTERFACE_MODE_RGMII_ID) {
ret = at803x_enable_rx_delay(phydev);
if (ret < 0)
return ret;
}
Looking at this code, one might believe that "rgmii rx clock delay"
is only enabled when the user requests it (through DT).
http://www.redeszone.net/app/uploads/2014/04/AR8035.pdf
cf. PDF page 48
*However* this bit is set to 1 at reset (both HW and SW resets).
Thus, "rgmii rx clock delay" is always enabled, whether the user
requests it or not.
Could someone knowledgeable comment on the expected behavior of
enabling rgmii rx (and tx) clock delay?
https://en.wikipedia.org/wiki/Media-independent_interface#Reduced_gigabit_media-independent_interface
Regards.
next prev parent reply other threads:[~2016-11-04 13:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 15:29 Ethernet not working on a different SoC with same eth HW Mason
2016-10-31 15:37 ` Andrew Lunn
2016-10-31 15:48 ` Mason
2016-10-31 15:53 ` Andrew Lunn
2016-10-31 16:28 ` Mason
2016-11-04 13:01 ` Mason [this message]
2016-11-04 13:40 ` Måns Rullgård
2016-11-04 13:51 ` Mason
2016-11-04 13:57 ` Andrew Lunn
2016-11-04 14:01 ` Sebastian Frias
2016-11-04 14:04 ` Måns Rullgård
2016-11-04 14:13 ` Mason
2016-11-04 14:22 ` Andrew Lunn
2016-11-04 15:05 ` Måns Rullgård
2016-11-04 15:17 ` Andrew Lunn
2016-11-04 15:22 ` Måns Rullgård
2016-11-04 16:45 ` Florian Fainelli
2016-11-04 16:55 ` Måns Rullgård
2016-11-04 17:06 ` Mason
2016-10-31 15:39 ` Andrew Lunn
2016-11-08 15:41 ` Mason
2016-11-09 17:38 ` Mason
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=581C8691.2060306@free.fr \
--to=slash.tmp@free.fr \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=mans@mansr.com \
--cc=martin.blumenstingl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=sf84@laposte.net \
--cc=timur@codeaurora.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zefir.kurtisi@neratec.com \
--cc=zonque@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.