From: Andrew Lunn <andrew@lunn.ch>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Mason <slash.tmp@free.fr>, netdev <netdev@vger.kernel.org>,
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 15:22:23 +0100 [thread overview]
Message-ID: <20161104142223.GD3600@lunn.ch> (raw)
In-Reply-To: <yw1xtwbnjq88.fsf@unicorn.mansr.com>
> > I agree with you. But fixing it is likely to break boards which
> > currently have "rgmii", but actually need the delay in order to work.
>
> Does the internal delay here refer to the PHY or the MAC? It's a
> property of the MAC node after all.
It is the PHY which applies the delay.
The phy-mode property is in the MAC part of the device tree binding,
but the delay is not the primary purpose of this property. Its primary
purpose, RGMII, RMII, SGMII, etc, is applicable to both the MAC and
the PHY. It probably would of been better to have the delays as a
separate property, but that is not how it is...
Andrew
next prev parent reply other threads:[~2016-11-04 14:22 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
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 [this message]
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=20161104142223.GD3600@lunn.ch \
--to=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=slash.tmp@free.fr \
--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 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).