From: Geert Uytterhoeven <geert+renesas@glider.be>
To: "Sergey Shtylyov" <s.shtylyov@omp.ru>,
"Paul Barker" <paul.barker.ct@bp.renesas.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Claudiu Beznea" <claudiu.beznea.uj@bp.renesas.com>,
"Biju Das" <biju.das.jz@bp.renesas.com>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH net-next v2 0/2] ravb: Add MII support for R-Car V4M
Date: Mon, 24 Jun 2024 15:25:23 +0200 [thread overview]
Message-ID: <cover.1719234830.git.geert+renesas@glider.be> (raw)
Hi all,
All EtherAVB instances on R-Car Gen3/Gen4 SoCs support the RGMII
interface. In addition, the first two EtherAVB instances on R-Car V4M
also support the MII interface, but this is not yet supported by the
driver. This patch series adds support for MII on R-Car Gen4, after the
customary cleanup.
Changes compared to v1[1]:
- New patch "ravb: Improve ravb_hw_info instance order",
- Add Reviewed-by,
- Rename ravb_emac_init_rcar_apsr() to ravb_emac_init_rcar_gen4(),
- Restrict MII support to R-Car Gen4 by adding a new ravb_hw_info
instance.
The corresponding pin control support is available in [2].
Compile-tested only, as all AVB interfaces on the Gray Hawk Single
development board are connected to RGMII PHYs.
No regressions on R-Car V4H.
Thanks for your comments!
[1] "[PATCH/RFC] net: ravb: Add MII support for R-Car V4M"
https://lore.kernel.org/f0ef3e00aec461beb33869ab69ccb44a23d78f51.1718378166.git.geert+renesas@glider.be
[2] "[PATCH/RFC] pinctrl: renesas: r8a779h0: Add AVB MII pins and groups"
https://lore.kernel.org/4a0a12227f2145ef53b18bc08f45b19dcd745fc6.1718378739.git.geert+renesas@glider.be/
Geert Uytterhoeven (2):
ravb: Improve ravb_hw_info instance order
ravb: Add MII support for R-Car V4M
drivers/net/ethernet/renesas/ravb.h | 1 +
drivers/net/ethernet/renesas/ravb_main.c | 45 +++++++++++++++++++++---
2 files changed, 41 insertions(+), 5 deletions(-)
--
2.34.1
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 reply other threads:[~2024-06-24 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 13:25 Geert Uytterhoeven [this message]
2024-06-24 13:25 ` [PATCH net-next v2 1/2] ravb: Improve ravb_hw_info instance order Geert Uytterhoeven
2024-06-24 15:42 ` Niklas Söderlund
2024-06-24 20:11 ` Sergey Shtylyov
2024-06-24 13:25 ` [PATCH net-next v2 2/2] ravb: Add MII support for R-Car V4M Geert Uytterhoeven
2024-06-24 20:29 ` Sergey Shtylyov
2024-06-26 0:10 ` [PATCH net-next v2 0/2] " patchwork-bot+netdevbpf
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=cover.1719234830.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=s.shtylyov@omp.ru \
/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).