netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Mason <slash.tmp@free.fr>, Sebastian Frias <sf84@laposte.net>,
	netdev@vger.kernel.org
Cc: davem@davemloft.net, andrew@lunn.ch,
	martin.blumenstingl@googlemail.com, mans@mansr.com,
	alexandre.torgue@st.com, peppe.cavallaro@st.com,
	timur@codeaurora.org, jbrunet@baylibre.com
Subject: Re: [PATCH net-next v2 3/4] Documentation: net: phy: Add blurb about RGMII
Date: Mon, 28 Nov 2016 11:47:44 -0800	[thread overview]
Message-ID: <c4146d81-712e-0f8d-f7f3-4a229efd99e6@gmail.com> (raw)
In-Reply-To: <b6a19ca6-8bda-8573-eb7b-9ed7f80ca480@free.fr>

On 11/28/2016 11:15 AM, Mason wrote:
> On 28/11/2016 18:43, Florian Fainelli wrote:
> 
>> On 11/28/2016 02:34 AM, Sebastian Frias wrote:
>>
>>> For what is worth, the Atheros at803x driver comes with RX delay enabled
>>> as per HW reset.
>>
>> Always, or is this a behavior possibly defined via a stra-pin that can
>> be changed?
> 
> Here's the data sheet:
> 
>   http://www.redeszone.net/app/uploads/2014/04/AR8035.pdf
> 
> 4.2.25 rgmii rx clock delay control
> Offset: 0x00
> bit 15: Control bit for rgmii interface rx clock delay:
> 1 = rgmii rx clock delay enable
> 0 = rgmii rx clock delay disable
> HW Rst. 1
> SW Rst. 1
> 
> As far as I can tell, rx delay is enabled by default, always.
> 
> The "Features" list mentions
> "RGMII timing modes support internal delay and external delay on Rx path"
> (Not sure about the internal vs external distinction.)
> 
> Table 3-6. RGMII AC Characteristics — no Internal Delay
> Table 3-7. RGMII AC Characteristics — with internal delay added (Default)
> 
> Delay is 2 ns apparently.
> 
> There's also
> 4.2.27 Hib ctrl and rgmii gtx clock delay register
> Offset: 0x0B
> 
> bits 6:5 Gtx_dly_val
> Select the delay of gtx_clk.
> 00:0.25ns
> 01:1.3ns
> 10:2.4ns
> 11:3.4ns
> 
> I don't know what that is used for.
> Maybe this is the external vs internal delay?

First, this has little to do with the initial patch series being
discussed now, and second, this still looks like an internal delay
programming, just that it applies to the received transmit clock from
the MAC, that's how I read it though.
-- 
Florian

  reply	other threads:[~2016-11-28 19:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 18:44 [PATCH net-next v2 0/4] Documentation: net: phy: Improve documentation Florian Fainelli
2016-11-27 18:44 ` [PATCH net-next v2 1/4] Documentation: net: phy: remove description of function pointers Florian Fainelli
2016-11-27 18:44 ` [PATCH net-next v2 2/4] Documentation: net: phy: Add a paragraph about pause frames/flow control Florian Fainelli
2016-11-28 10:38   ` Sebastian Frias
2016-11-28 17:33     ` Florian Fainelli
2016-11-30 13:20       ` Sebastian Frias
2016-11-27 18:44 ` [PATCH net-next v2 3/4] Documentation: net: phy: Add blurb about RGMII Florian Fainelli
2016-11-27 22:24   ` Timur Tabi
2016-11-27 23:02     ` Florian Fainelli
2016-11-30 12:32       ` David Laight
2016-11-30 13:43         ` Måns Rullgård
2016-11-28 10:34   ` Sebastian Frias
2016-11-28 17:43     ` Florian Fainelli
2016-11-28 19:15       ` Mason
2016-11-28 19:47         ` Florian Fainelli [this message]
2016-11-27 18:44 ` [PATCH net-next v2 4/4] Documentation: net: phy: Add links to several standards documents Florian Fainelli
2016-11-27 20:32 ` [PATCH net-next v2 0/4] Documentation: net: phy: Improve documentation Martin Blumenstingl

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=c4146d81-712e-0f8d-f7f3-4a229efd99e6@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=alexandre.torgue@st.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=jbrunet@baylibre.com \
    --cc=mans@mansr.com \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=sf84@laposte.net \
    --cc=slash.tmp@free.fr \
    --cc=timur@codeaurora.org \
    /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).