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 02/12] can: rcar_canfd: Fix typos in macro names
Date: Wed, 11 Nov 2026 11:51:32 +0000 [thread overview]
Message-ID: <sashiko-outbox-208904@kernel.org> (raw)
In-Reply-To: <20261110115112.3807247-3-mkl@pengutronix.de>
Thank you for your contribution! Sashiko AI review found no new issues
in this patch, but noticed 1 related pre-existing issue it does not
introduce:
- [Medium] can: rcar_canfd: missing hardware reset on rcar_canfd_start()
timeout [1]
--
commit 683df0154ce2ae541ee019a38062ac1a2b103eac
Author: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
can: rcar_canfd: Fix typos in macro names
This commit renames the RCANFD_CCTR_CHDMC_* channel mode macros to
RCANFD_CCTR_CHMDC_* to match the hardware register documentation.
Link: https://patch.msgid.link/20260902141544.565763-3-claudiu.beznea+renesas@tuxon.dev
> diff --git a/drivers/net/can/rcar/rcar_canfd.c b/drivers/net/can/rcar/rcar_canfd.c
> index fcc37b73ed436..b7c4fe3477ac5 100644
> --- a/drivers/net/can/rcar/rcar_canfd.c
> +++ b/drivers/net/can/rcar/rcar_canfd.c
[ ... ]
> @@ -1504,7 +1504,7 @@ static int rcar_canfd_start(struct net_device *ndev)
>
> /* Set channel to Operational mode */
> rcar_canfd_update_bit(priv->base, RCANFD_CCTR(ch),
> - RCANFD_CCTR_CHMDC_MASK, RCANFD_CCTR_CHDMC_COPM);
> + RCANFD_CCTR_CHMDC_MASK, RCANFD_CCTR_CHMDC_COPM);
>
> /* Verify channel mode change */
> err = readl_poll_timeout((priv->base + RCANFD_CSTS(ch)), sts,
[Severity: Medium]
This problem wasn't introduced by this patch, but does the error path in
rcar_canfd_start() [1] leave RCANFD_CCTR_CHMDC_COPM pending in
hardware if readl_poll_timeout() times out?
Neither the fail_mode_change path in rcar_canfd_start() nor the out_close
unwind path in rcar_canfd_open() transitions the channel back to
RCANFD_CCTR_CHMDC_CRESET:
drivers/net/can/rcar/rcar_canfd.c:rcar_canfd_start() {
...
err = readl_poll_timeout((priv->base + RCANFD_CSTS(ch)), sts,
(sts & RCANFD_CSTS_COMSTS), 2, 500000);
if (err) {
netdev_err(ndev, "channel %u communication state failed\n", ch);
goto fail_mode_change;
}
...
fail_mode_change:
rcar_canfd_disable_channel_interrupts(priv);
return err;
}
On a later open attempt, rcar_canfd_set_bittiming() runs while the channel
is no longer in reset mode, so the hardware ignores the bit-timing
configuration writes.
[1] https://sashiko.dev/#/bug/linux-f4b05dc8-33ba-4ce4-8f99-3c391b0fc79a
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110115112.3807247-1-mkl@pengutronix.de?part=2
next prev parent reply other threads:[~2026-11-11 11:51 UTC|newest]
Thread overview: 28+ 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-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 [this message]
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-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-208904@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox