From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Oleksij Rempel <linux@rempel-privat.de>,
Philippe Schenker <philippe.schenker@toradex.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Dan Murphy <dmurphy@ti.com>,
Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Magnus Damm <magnus.damm@gmail.com>,
netdev <netdev@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v4 0/5] net/ravb: Add support for explicit internal clock delay configuration
Date: Wed, 30 Sep 2020 14:21:30 +0200 [thread overview]
Message-ID: <CAMuHMdU2k5MmUe2_g7a9268XG2=9phiWoaSTeQ9ZbxoAs3QFfw@mail.gmail.com> (raw)
In-Reply-To: <20200917135707.12563-1-geert+renesas@glider.be>
Hi David, Jakub,
On Thu, Sep 17, 2020 at 3:57 PM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> 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.
>
> This can be considered the MAC counterpart of commit 9150069bf5fc0e86
> ("dt-bindings: net: Add tx and rx internal delays"), which applies to
> the PHY. Note that unlike commit 92252eec913b2dd5 ("net: phy: Add a
> helper to return the index for of the internal delay"), no helpers are
> provided to parse the DT properties, as so far there is a single user
> only, which supports only zero or a single fixed value. Of course such
> helpers can be added later, when the need arises, or when deemed useful
> otherwise.
>
> This series consists of 3 parts:
> 1. DT binding updates documenting the new properties, for both the
> generic ethernet-controller and the EtherAVB-specific bindings,
> 2. Conversion to json-schema of the Renesas EtherAVB DT bindings.
> Technically, the conversion is independent of all of the above.
> I included it in this series, as it shows how all sanity checks on
> "[rt]x-internal-delay-ps" values are implemented as DT binding
> checks,
> 3. EtherAVB driver update implementing support for the new properties.
>
> Given Rob has provided his acks for the DT binding updates, all of this
> can be merged through net-next.
>
> Changes compared to v3[4]:
> - Add Reviewed-by,
> - Drop the DT updates, as they will be merged through renesas-devel and
> arm-soc, and have a hard dependency on this series.
>
> Changes compared to v2[5]:
> - Update recently added board DTS files,
> - Add Reviewed-by.
>
> Changes compared to v1[6]:
> - Added "[PATCH 1/7] dt-bindings: net: ethernet-controller: Add
> internal delay properties",
> - Replace "renesas,[rt]xc-delay-ps" by "[rt]x-internal-delay-ps",
> - Incorporated EtherAVB DT binding conversion to json-schema,
> - Add Reviewed-by.
>
> Impacted, tested:
> - Salvator-X(S) with R-Car H3 ES1.0 and ES2.0, M3-W, and M3-N.
>
> Not impacted, tested:
> - Ebisu with R-Car E3.
>
> Impacted, not tested:
> - Salvator-X(S) with other SoC variants,
> - ULCB with R-Car H3/M3-W/M3-N variants,
> - V3MSK and Eagle with R-Car V3M,
> - Draak with R-Car V3H,
> - HiHope RZ/G2[MN] with RZ/G2M or RZ/G2N,
> - Beacon EmbeddedWorks RZ/G2M Development Kit.
>
> To ease testing, I have pushed this series and the DT updates to the
> topic/ravb-internal-clock-delays-v4 branch of my renesas-drivers
> repository at
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git.
>
> Thanks for applying!
Is there anything still blocking this series?
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-09-30 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 13:57 Geert Uytterhoeven
2020-09-17 13:57 ` [PATCH net-next v4 1/5] dt-bindings: net: ethernet-controller: Add internal delay properties Geert Uytterhoeven
2020-09-17 13:57 ` [PATCH net-next v4 2/5] dt-bindings: net: renesas,ravb: Document internal clock " Geert Uytterhoeven
2020-09-17 13:57 ` [PATCH net-next v4 3/5] dt-bindings: net: renesas,etheravb: Convert to json-schema Geert Uytterhoeven
2020-09-17 13:57 ` [PATCH net-next v4 4/5] ravb: Split delay handling in parsing and applying Geert Uytterhoeven
2020-09-17 13:57 ` [PATCH net-next v4 5/5] ravb: Add support for explicit internal clock delay configuration Geert Uytterhoeven
2020-09-17 18:49 ` Dan Murphy
2020-09-18 9:04 ` Geert Uytterhoeven
2020-09-30 12:21 ` Geert Uytterhoeven [this message]
2020-09-30 21:19 ` [PATCH net-next v4 0/5] net/ravb: " David Miller
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='CAMuHMdU2k5MmUe2_g7a9268XG2=9phiWoaSTeQ9ZbxoAs3QFfw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=f.fainelli@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®