[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210924153113.10046-1-uli+renesas@fpond.eu>
Date: Fri, 24 Sep 2021 17:31:10 +0200
From: Ulrich Hecht <uli+renesas@...nd.eu>
To: linux-renesas-soc@...r.kernel.org
Cc: netdev@...r.kernel.org, davem@...emloft.net,
linux-can@...r.kernel.org, prabhakar.mahadev-lad.rj@...renesas.com,
biju.das.jz@...renesas.com, wsa@...nel.org,
yoshihiro.shimoda.uh@...esas.com, wg@...ndegger.com,
mkl@...gutronix.de, kuba@...nel.org, mailhol.vincent@...adoo.fr,
socketcan@...tkopp.net, Ulrich Hecht <uli+renesas@...nd.eu>
Subject: [PATCH 0/3] can: rcar_canfd: Add support for V3U flavor
Hi!
This adds CANFD support for V3U (R8A779A0) SoCs. The V3U's IP supports up to
eight channels and has some other minor differences to the Gen3 variety:
- changes to some register offsets and layouts
- absence of "classic CAN" registers, both modes are handled through the
CANFD register set
This patch set tries to accommodate these changes in a minimally intrusive
way. It follows the methods implemented in the BSP patch 745cdc4ea76af4
("can: rcar_canfd: Add support for r8a779a0 SoC"), but has not been tested
on an actual V3U device due to lack of hardware.
One thing I'm not sure of is what to name the compatible string. ATM it
looks to me like this controller cultivar is a one-off, so I named it
"renesas,r8a779a0-canfd", but I would not be surprised if it showed up in
future chips as well.
CU
Uli
Ulrich Hecht (3):
can: rcar_canfd: Add support for r8a779a0 SoC
dt-bindings: can: renesas,rcar-canfd: Document r8a779a0 support
arm64: dts: r8a779a0: Add CANFD device node
.../bindings/net/can/renesas,rcar-canfd.yaml | 1 +
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 55 +++++
drivers/net/can/rcar/rcar_canfd.c | 227 ++++++++++++------
3 files changed, 208 insertions(+), 75 deletions(-)
--
2.20.1
Powered by blists - more mailing lists