From: sashiko-bot@kernel.org
To: "Marc Kleine-Budde" <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org,
"Oliver Hartkopp" <socketcan@hartkopp.net>,
"Vincent Mailhol" <mailhol@kernel.org>,
"Oleksij Rempel" <o.rempel@pengutronix.de>
Subject: Re: [PATCH net-next 07/12] can: rcar_canfd: Use DT clock names in the probe message
Date: Wed, 11 Nov 2026 11:51:34 +0000 [thread overview]
Message-ID: <sashiko-outbox-208909@kernel.org> (raw)
In-Reply-To: <20261110115112.3807247-8-mkl@pengutronix.de>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] can: rcar_canfd: wrong DT clock name logged in
rcar_canfd_probe()
--
commit 465506d0bf0262439ace49568aa154d5d5ff9172
Author: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
can: rcar_canfd: Use DT clock names in the probe message
This commit updates the probe log message in rcar_canfd_probe() to report
the DT binding clock names ("can_clk", "fck", or "canfd") for the selected
clock.
Link: https://patch.msgid.link/20261019121356.2421761-3-claudiu.beznea@kernel.org
> diff --git a/drivers/net/can/rcar/rcar_canfd.c b/drivers/net/can/rcar/rcar_canfd.c
> index bb2d03b75142a..4f5cdfa8211da 100644
> --- a/drivers/net/can/rcar/rcar_canfd.c
> +++ b/drivers/net/can/rcar/rcar_canfd.c
> @@ -2312,7 +2312,7 @@ static int rcar_canfd_probe(struct platform_device *pdev)
>
> platform_set_drvdata(pdev, gpriv);
> dev_info(dev, "global operational state (%s clk, %s mode)\n",
> - gpriv->extclk ? "ext" : "canfd",
> + gpriv->extclk ? "can_clk" : (info->fcan_pclk ? "fck" : "canfd"),
> gpriv->fdmode ? (gpriv->fd_only_mode ? "fd-only" : "fd") : "classical");
[Severity: Low]
Does checking gpriv->extclk here log "canfd" instead of "can_clk" on SoCs
using r9a09g047_hw_info (such as RZ/G3E, RZ/V2N, and RZ/V2H)?
Those SoCs define their fCAN clock under the DT name "can_clk", so
devm_clk_get_optional(dev, "can_clk") succeeds with a non-zero rate and
rcar_canfd_probe() sets:
drivers/net/can/rcar/rcar_canfd.c:rcar_canfd_probe() {
...
} else {
fcan_freq = clk_get_rate(gpriv->can_clk);
gpriv->extclk = gpriv->info->external_clk;
}
}
Because r9a09g047_hw_info has both .external_clk = 0 and .fcan_pclk = 0,
gpriv->extclk is false even though the "can_clk" DT clock was selected,
causing dev_info() to report "canfd clk".
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110115112.3807247-1-mkl@pengutronix.de?part=7
next prev parent reply other threads:[~2026-11-11 11:51 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 [this message]
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=sashiko-outbox-208909@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=sashiko-reviews@lists.linux.dev \
--cc=socketcan@hartkopp.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.