All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mason <slash.tmp@free.fr>
To: Mans Rullgard <mans@mansr.com>, Andrew Lunn <andrew@lunn.ch>
Cc: 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:13:45 +0100	[thread overview]
Message-ID: <581C9799.3040101@free.fr> (raw)
In-Reply-To: <yw1xtwbnjq88.fsf@unicorn.mansr.com>

On 04/11/2016 15:04, Måns Rullgård wrote:

> Andrew Lunn <andrew@lunn.ch> writes:
> 
>>> Considering the ethernet DT bindings:
>>>
>>> https://www.kernel.org/doc/Documentation/devicetree/bindings/net/ethernet.txt
>>>
>>> Specifically, phy-mode values "rgmii", "rgmii-id", "rgmii-rxid", "rgmii-txid".
>>>
>>> Assuming that "rxid" (rx internal delay) and "rx clock delay" are
>>> in fact the same concept with different names, do you agree that
>>> it would be unexpected for "rgmii rx clock delay" to be enabled
>>> when a DTB specifies "rgmii" or "rgmii-txid" ?
>>
>> 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.

Isn't there a one-to-one correspondence between MAC and PHY?

Can a MAC be connected to multiple PHYs?
Can a PHY be connected to multiple MACs?

If it is a one-to-one correspondence, then whether the
property is specified in the MAC or PHY node is just a
matter of presentation, IMHO.

Regards.

  reply	other threads:[~2016-11-04 14:14 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 [this message]
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=581C9799.3040101@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.