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 16:17:44 +0100 [thread overview]
Message-ID: <20161104151744.GG3600@lunn.ch> (raw)
In-Reply-To: <yw1xpombjnfn.fsf@unicorn.mansr.com>
On Fri, Nov 04, 2016 at 03:05:00PM +0000, Måns Rullgård wrote:
> Andrew Lunn <andrew@lunn•ch> writes:
>
> >> > 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.
>
> Says who?
The source code.
> Some MACs can do it too.
I'm sure they can. But look at the code. Nearly none do, and those
that do are potentially broken.
> There is also no way to specify the amount of delay required even though
> many devices support more than one value.
Those PHYs that which support variable delays add there own device
tree properties. See for example Micrel KSZ9021/KSZ9031 Gigabit Ethernet PHY
Andrew
next prev parent reply other threads:[~2016-11-04 15:17 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
2016-11-04 15:05 ` Måns Rullgård
2016-11-04 15:17 ` Andrew Lunn [this message]
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=20161104151744.GG3600@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=f.fainelli@gmail$(echo .)com \
--cc=mans@mansr$(echo .)com \
--cc=martin.blumenstingl@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sergei.shtylyov@cogentembedded$(echo .)com \
--cc=sf84@laposte$(echo .)net \
--cc=slash.tmp@free$(echo .)fr \
--cc=timur@codeaurora$(echo .)org \
--cc=u.kleine-koenig@pengutronix$(echo .)de \
--cc=zefir.kurtisi@neratec$(echo .)com \
--cc=zonque@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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