From: Phil Edworthy <phil.edworthy@renesas.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Phil Edworthy <phil.edworthy@renesas.com>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-clk@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: [PATCH 0/9] Add Renesas RZ/V2M Ethernet support
Date: Wed, 4 May 2022 15:54:45 +0100 [thread overview]
Message-ID: <20220504145454.71287-1-phil.edworthy@renesas.com> (raw)
The RZ/V2M Ethernet is very similar to R-Car Gen3 Ethernet-AVB, though
some small parts are the same as R-Car Gen2.
Other differences are:
* It has separate data (DI), error (Line 1) and management (Line 2) irqs
rather than one irq for all three.
* Instead of using the High-speed peripheral bus clock for gPTP, it has
a separate gPTP reference clock.
The dts patches depend on v4 of the following patch set:
"Add new Renesas RZ/V2M SoC and Renesas RZ/V2M EVK support"
Phil Edworthy (9):
clk: renesas: r9a09g011: Add eth clock and reset entries
dt-bindings: net: renesas,etheravb: Document RZ/V2M SoC
ravb: Separate use of GIC reg for PTME from multi_irqs
ravb: Separate handling of irq enable/disable regs into feature
ravb: Support separate Line0 (Desc), Line1 (Err) and Line2 (Mgmt) irqs
ravb: Use separate clock for gPTP
ravb: Add support for RZ/V2M
arm64: dts: renesas: r9a09g011: Add ethernet nodes
arm64: dts: renesas: rzv2m evk: Enable ethernet
.../bindings/net/renesas,etheravb.yaml | 82 ++++++++++++-----
.../boot/dts/renesas/r9a09g011-v2mevk2.dts | 14 +++
arch/arm64/boot/dts/renesas/r9a09g011.dtsi | 51 +++++++++++
drivers/clk/renesas/r9a09g011-cpg.c | 14 +--
drivers/net/ethernet/renesas/ravb.h | 7 ++
drivers/net/ethernet/renesas/ravb_main.c | 89 +++++++++++++++++--
drivers/net/ethernet/renesas/ravb_ptp.c | 4 +-
7 files changed, 228 insertions(+), 33 deletions(-)
--
2.32.0
next reply other threads:[~2022-05-04 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 14:54 Phil Edworthy [this message]
2022-05-04 14:54 ` [PATCH 1/9] clk: renesas: r9a09g011: Add eth clock and reset entries Phil Edworthy
2022-05-05 9:19 ` Geert Uytterhoeven
2022-05-05 0:57 ` [PATCH 0/9] Add Renesas RZ/V2M Ethernet support Jakub Kicinski
2022-05-05 6:59 ` Geert Uytterhoeven
2022-05-05 9:14 ` Phil Edworthy
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=20220504145454.71287-1-phil.edworthy@renesas.com \
--to=phil.edworthy@renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=sboyd@kernel.org \
--cc=sergei.shtylyov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox