[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <yw1xzikh3wxl.fsf@unicorn.mansr.com>
Date: Wed, 30 Nov 2016 13:43:34 +0000
From: Måns Rullgård <mans@...sr.com>
To: David Laight <David.Laight@...LAB.COM>
Cc: 'Florian Fainelli' <f.fainelli@...il.com>,
Timur Tabi <timur@...eaurora.org>,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
"davem\@davemloft.net" <davem@...emloft.net>,
"andrew\@lunn.ch" <andrew@...n.ch>,
"sf84\@laposte.net" <sf84@...oste.net>,
"martin.blumenstingl\@googlemail.com"
<martin.blumenstingl@...glemail.com>,
"alexandre.torgue\@st.com" <alexandre.torgue@...com>,
"peppe.cavallaro\@st.com" <peppe.cavallaro@...com>,
"jbrunet\@baylibre.com" <jbrunet@...libre.com>
Subject: Re: [PATCH net-next v2 3/4] Documentation: net: phy: Add blurb about RGMII
David Laight <David.Laight@...LAB.COM> writes:
> From: Florian Fainelli
>> Sent: 27 November 2016 23:03
>> Le 27/11/2016 14:24, Timur Tabi a crit :
>> >> + * PHY device drivers in PHYLIB being reusable by nature, being able to
>> >> + configure correctly a specified delay enables more designs with
>> >> similar delay
>> >> + requirements to be operate correctly
>> >
>> > Ok, this one I don't know how to fix. I'm not really sure what you're
>> > trying to say.
>>
>> What I am trying to say is that once a PHY driver properly configures a
>> delay that you have specified, there is no reason why this is not
>> applicable to other platforms using this same PHY driver.
>
> As has been stated earlier it can depend on the track lengths on the
> board itself.
> (Although 1ns is about 1 foot - so track delays of that length are unlikely.)
There could be a delay element.
--
Måns Rullgård
Powered by blists - more mailing lists