Linux CAN drivers development
 help / color / mirror / Atom feed
From: netdev-bot+sashiko@kernel.org
To: 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, geert+renesas@glider.be
Subject: Re: [PATCH net-next 10/12] can: rcar_canfd: Document that RZ/G3S has no Classical CAN mode
Date: Wed, 11 Nov 2026 12:20:23 +0000	[thread overview]
Message-ID: <179439962315.2199510.11528694161549398887@kernel.org> (raw)
In-Reply-To: <20261110115112.3807247-11-mkl@pengutronix.de>

Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.

Low priority / nit picks for your consideration:

- [Low] The patch fixes only half of the header comment in
  drivers/net/can/rcar/rcar_canfd.c.

--

can: rcar_canfd: Document that RZ/G3S has no Classical CAN mode

This patch changes the header comments in the R-Car CAN FD driver to say
that RZ/G3S does not support Classical CAN (CAN 2.0) only mode. It
matches the corresponding dt-bindings update. There is no functional
change.

Link: https://patch.msgid.link/20261021-canfd_rzg3l-v6-2-b4abfdba8e70@bp.renesas.com

> diff --git a/drivers/net/can/rcar/rcar_canfd.c b/drivers/net/can/rcar/rcar_canfd.c
> index 4f5cdfa8211da..072987316cc75 100644
> --- a/drivers/net/can/rcar/rcar_canfd.c
> +++ b/drivers/net/can/rcar/rcar_canfd.c
> @@ -6,7 +6,7 @@
>  
>  /* The R-Car CAN FD controller can operate in either one of the below two modes
>   *  - CAN FD only mode
> - *  - Classical CAN (CAN 2.0) only mode
> + *  - Classical CAN (CAN 2.0) only mode (Except RZ/G3S)
>   *
>   * This driver puts the controller in CAN FD only mode by default. In this
>   * mode, the controller acts as a CAN FD node that can also interoperate with

[Severity: Low]
This isn't a bug, but should the paragraph just below this one in the same
header comment get the RZ/G3S exception too? The patch leaves it as is:

drivers/net/can/rcar/rcar_canfd.c:
 * To switch the controller to Classical CAN (CAN 2.0) only mode, add
 * "renesas,no-can-fd" optional property to the device tree node. A h/w reset is
 * also required to switch modes.

The renesas,rcar-canfd.yaml binding does not allow this property on RZ/G3S.
The allOf branch for renesas,r9a08g045-canfd has:

    then:
      properties:
        renesas,no-can-fd: false
        renesas,fd-only: false

So the comment now says Classical CAN mode is not available on RZ/G3S, but
the next paragraph still tells readers to add renesas,no-can-fd, without
naming any SoC that cannot use it.

Later in the series, "can: rcar_canfd: Add support for Renesas RZ/G3L"
changes only the line above to "(Except RZ/G3{L,S})" and leaves this
paragraph as it is.

Could the instruction paragraph also say that renesas,no-can-fd must not
be used on RZ/G3S?

[ ... ]

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261110115112.3807247-2-mkl%40pengutronix.de

  reply	other threads:[~2026-11-11 12:20 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
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 [this message]
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=179439962315.2199510.11528694161549398887@kernel.org \
    --to=netdev-bot+sashiko@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 \
    /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