From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
claudiu.beznea.uj@bp.renesas.com, robh@kernel.org,
geert+renesas@glider.be
Subject: Re: [PATCH net-next 01/12] dt-bindings: can: renesas,rcar-canfd: Document RZ/G3S SoC
Date: Thu, 12 Nov 2026 18:30:17 +0000 [thread overview]
Message-ID: <179450821702.579048.3144753075880171787.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110115112.3807247-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Tue, 10 Nov 2026 12:41:24 +0100 you wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> The CAN FD controller found on the Renesas RZ/G3S SoC is largely compatible
> with the variant present on the RZ/G3E SoC. The main differences are:
> - the RZ/G3S provides only two CAN FD channels
> - the RZ/G3S supports only CAN FD operation; the Channel n CAN FD
> Configuration Register does not implement the bits used to select
> classical CAN-only mode (bit 30) or CAN FD-only mode (bit 28);
> consequently, bit 31 (CAN FD Frame Distinction Enable) of the same
> register is also not implemented
> - some bits in several registers (mainly reserved or status bits) are
> read-write on the RZ/G3S but read-only on the RZ/G3E; their behavior is
> otherwise identical: the bits read back as 0 on both SoCs and software
> is allowed to write only 0 to them on the RZ/G3S
> - the RZ/G3S provides 256 acceptance filters, compared to 768 on the
> RZ/G3E
> - the RZ/G3S can use PCLK clock as the CAN FD clock source through an
> internal clock divider, while also supporting an external CAN FD clock
> source
>
> [...]
Here is the summary with links:
- [net-next,01/12] dt-bindings: can: renesas,rcar-canfd: Document RZ/G3S SoC
https://git.kernel.org/netdev/net-next/c/7aa321a595e2
- [net-next,02/12] can: rcar_canfd: Fix typos in macro names
https://git.kernel.org/netdev/net-next/c/79d4ac8cc434
- [net-next,03/12] can: rcar_canfd: Allow the CAN FD clock to be sourced from fck
https://git.kernel.org/netdev/net-next/c/b40631d86a8d
- [net-next,04/12] can: rcar_canfd: Do not set registers selecting the CAN mode
https://git.kernel.org/netdev/net-next/c/a2af960288df
- [net-next,05/12] can: rcar_canfd: Add support for Renesas RZ/G3S
https://git.kernel.org/netdev/net-next/c/32e8a013243c
- [net-next,06/12] can: rcar_canfd: Check can_clk request for errors
https://git.kernel.org/netdev/net-next/c/0deb654e2b6b
- [net-next,07/12] can: rcar_canfd: Use DT clock names in the probe message
https://git.kernel.org/netdev/net-next/c/6a6c71a03d5a
- [net-next,08/12] dt-bindings: can: renesas,rcar-canfd: Restrict resets in top-level
https://git.kernel.org/netdev/net-next/c/3696939f7cb5
- [net-next,09/12] dt-bindings: can: renesas,rcar-canfd: Simplify renesas,no-can-fd description
https://git.kernel.org/netdev/net-next/c/aecb16f09db9
- [net-next,10/12] can: rcar_canfd: Document that RZ/G3S has no Classical CAN mode
https://git.kernel.org/netdev/net-next/c/7a5305fb26cd
- [net-next,11/12] dt-bindings: can: renesas,rcar-canfd: Document RZ/G3L SoC
https://git.kernel.org/netdev/net-next/c/0e890f327d8d
- [net-next,12/12] can: rcar_canfd: Add support for Renesas RZ/G3L
https://git.kernel.org/netdev/net-next/c/aa56fb023365
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-11-12 18:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 11:41 [PATCH net-next 0/12] pull-request: can-next 2026-11-10 Marc Kleine-Budde
2026-11-10 11:41 ` [PATCH net-next 01/12] dt-bindings: can: renesas,rcar-canfd: Document RZ/G3S SoC Marc Kleine-Budde
2026-11-11 11:51 ` sashiko-bot
2026-11-11 12:20 ` netdev-bot+sashiko
2026-11-12 18:30 ` patchwork-bot+netdevbpf [this message]
2026-11-10 11:41 ` [PATCH net-next 02/12] can: rcar_canfd: Fix typos in macro names Marc Kleine-Budde
2026-11-11 11:51 ` sashiko-bot
2026-11-10 11:41 ` [PATCH net-next 03/12] can: rcar_canfd: Allow the CAN FD clock to be sourced from fck Marc Kleine-Budde
2026-11-11 11:51 ` sashiko-bot
2026-11-11 12:20 ` netdev-bot+sashiko
2026-11-10 11:41 ` [PATCH net-next 04/12] can: rcar_canfd: Do not set registers selecting the CAN mode Marc Kleine-Budde
2026-11-10 11:41 ` [PATCH net-next 05/12] can: rcar_canfd: Add support for Renesas RZ/G3S Marc Kleine-Budde
2026-11-11 12:20 ` netdev-bot+sashiko
2026-11-10 11:41 ` [PATCH net-next 06/12] can: rcar_canfd: Check can_clk request for errors Marc Kleine-Budde
2026-11-11 12:20 ` netdev-bot+sashiko
2026-11-10 11:41 ` [PATCH net-next 07/12] can: rcar_canfd: Use DT clock names in the probe message Marc Kleine-Budde
2026-11-11 11:51 ` sashiko-bot
2026-11-11 12:01 ` Marc Kleine-Budde
2026-11-12 12:25 ` Marc Kleine-Budde
2026-11-12 13:39 ` claudiu beznea
2026-11-12 13:44 ` Marc Kleine-Budde
2026-11-12 18:20 ` Jakub Kicinski
2026-11-11 12:20 ` netdev-bot+sashiko
2026-11-10 11:41 ` [PATCH net-next 08/12] dt-bindings: can: renesas,rcar-canfd: Restrict resets in top-level Marc Kleine-Budde
2026-11-11 11:51 ` sashiko-bot
2026-11-11 12:20 ` netdev-bot+sashiko
2026-11-10 11:41 ` [PATCH net-next 09/12] dt-bindings: can: renesas,rcar-canfd: Simplify renesas,no-can-fd description Marc Kleine-Budde
2026-11-10 11:41 ` [PATCH net-next 10/12] can: rcar_canfd: Document that RZ/G3S has no Classical CAN mode Marc Kleine-Budde
2026-11-11 12:20 ` netdev-bot+sashiko
2026-11-10 11:41 ` [PATCH net-next 11/12] dt-bindings: can: renesas,rcar-canfd: Document RZ/G3L SoC Marc Kleine-Budde
2026-11-11 11:51 ` sashiko-bot
2026-11-11 12:20 ` netdev-bot+sashiko
2026-11-10 11:41 ` [PATCH net-next 12/12] can: rcar_canfd: Add support for Renesas RZ/G3L Marc Kleine-Budde
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=179450821702.579048.3144753075880171787.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=robh@kernel.org \
/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