All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: geert+renesas@glider.be
Cc: kuba@kernel.org, robh+dt@kernel.org, sergei.shtylyov@gmail.com,
	f.fainelli@gmail.com, andrew@lunn.ch, linux@rempel-privat.de,
	philippe.schenker@toradex.com, hkallweit1@gmail.com,
	dmurphy@ti.com, kazuya.mizuguchi.ks@renesas.com,
	wsa+renesas@sang-engineering.com, magnus.damm@gmail.com,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 resend 0/5] net/ravb: Add support for explicit internal clock delay configuration
Date: Thu, 01 Oct 2020 12:53:59 -0700 (PDT)	[thread overview]
Message-ID: <20201001.125359.1752693461501787622.davem@davemloft.net> (raw)
In-Reply-To: <20201001101008.14365-1-geert+renesas@glider.be>

From: Geert Uytterhoeven <geert+renesas@glider.be>
Date: Thu,  1 Oct 2020 12:10:03 +0200

> Some Renesas EtherAVB variants support internal clock delay
> configuration, which can add larger delays than the delays that are
> typically supported by the PHY (using an "rgmii-*id" PHY mode, and/or
> "[rt]xc-skew-ps" properties).
> 
> Historically, the EtherAVB driver configured these delays based on the
> "rgmii-*id" PHY mode.  This caused issues with PHY drivers that
> implement PHY internal delays properly[1].  Hence a backwards-compatible
> workaround was added by masking the PHY mode[2].
> 
> This patch series implements the next step of the plan outlined in [3],
> and adds proper support for explicit configuration of the MAC internal
> clock delays using new "[rt]x-internal-delay-ps" properties.  If none of
> these properties is present, the driver falls back to the old handling.
 ...

Series applied, thank you.

      parent reply	other threads:[~2020-10-01 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 10:10 [PATCH net-next v4 resend 0/5] net/ravb: Add support for explicit internal clock delay configuration Geert Uytterhoeven
2020-10-01 10:10 ` [PATCH net-next v4 resend 1/5] dt-bindings: net: ethernet-controller: Add internal delay properties Geert Uytterhoeven
2020-10-01 10:10 ` [PATCH net-next v4 resend 2/5] dt-bindings: net: renesas,ravb: Document internal clock " Geert Uytterhoeven
2020-10-01 10:10 ` [PATCH net-next v4 resend 3/5] dt-bindings: net: renesas,etheravb: Convert to json-schema Geert Uytterhoeven
2020-10-01 10:10 ` [PATCH net-next v4 resend 4/5] ravb: Split delay handling in parsing and applying Geert Uytterhoeven
2020-10-01 10:10 ` [PATCH net-next v4 resend 5/5] ravb: Add support for explicit internal clock delay configuration Geert Uytterhoeven
2020-10-01 19:53 ` David Miller [this message]

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=20201001.125359.1752693461501787622.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=f.fainelli@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=hkallweit1@gmail.com \
    --cc=kazuya.mizuguchi.ks@renesas.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=magnus.damm@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=philippe.schenker@toradex.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@gmail.com \
    --cc=wsa+renesas@sang-engineering.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.