From: sashiko-bot@kernel.org
To: "Zi-Yu Chen" <zychennvt@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3] arm64: dts: nuvoton: ma35d1: add CAN nodes
Date: Tue, 08 Sep 2026 01:54:35 +0000 [thread overview]
Message-ID: <20260908015435.7DE071F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260908014526.413399-1-zychennvt@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The CAN controller nodes omit the hardware `resets` property, despite the SoC providing dedicated CAN reset lines.
--
commit bc194563299d88a0e0b218c2bff6562e1d264119
Author: Zi-Yu Chen <zychennvt@gmail.com>
arm64: dts: nuvoton: ma35d1: add CAN nodes
This commit adds controller nodes for the four Bosch M_CAN blocks found
on the Nuvoton MA35D1 SoC. It also configures pinctrl, enables CAN1 and
CAN3 on the SOM board, and updates the APLL frequency.
> diff --git a/arch/arm64/boot/dts/nuvoton/ma35d1.dtsi b/arch/arm64/boot/dts/nuvoton/ma35d1.dtsi
> index 7228ad4735b5c..91c0abc1678f2 100644
> --- a/arch/arm64/boot/dts/nuvoton/ma35d1.dtsi
> +++ b/arch/arm64/boot/dts/nuvoton/ma35d1.dtsi
[ ... ]
> @@ -244,6 +244,58 @@ gpion: gpio@340 {
> };
> };
>
> + can0: can@403c0000 {
> + compatible = "bosch,m_can";
> + reg = <0x0 0x403c0000 0x0 0x200>, <0x0 0x403c0200 0x0 0x2000>;
> + reg-names = "m_can", "message_ram";
> + interrupts = <GIC_SPI 71 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 131 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "int0", "int1";
> + clocks = <&clk HCLK3>, <&clk CAN0_GATE>;
> + clock-names = "hclk", "cclk";
> + bosch,mram-cfg = <0x0 4 4 32 32 32 8 8>;
> + status = "disabled";
> + };
[Severity: Medium]
Should this node include the hardware resets property (e.g.,
resets = <&sys MA35D1_RESET_CANFD0>;)?
Without the hardware reset line, the bosch,m_can driver cannot perform a
hardware reset of the CAN controllers during probe or interface toggles.
It must rely solely on software initialization, which can fail to fully
recover the controller if the bootloader or a prior crashed state left
the hardware in an unpredictable state.
This omission pattern is identically repeated across the newly added can1,
can2, and can3 nodes below.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260908014526.413399-1-zychennvt@gmail.com?part=1
next prev parent reply other threads:[~2026-09-08 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 1:45 [PATCH v3] arm64: dts: nuvoton: ma35d1: add CAN nodes Zi-Yu Chen
2026-09-08 1:54 ` sashiko-bot [this message]
2026-09-11 2:15 ` Jacky Huang
2026-09-11 5:56 ` Marc Kleine-Budde
2026-09-12 11:02 ` Jacky Huang
2026-09-11 2:25 ` Jacky Huang
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=20260908015435.7DE071F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=zychennvt@gmail.com \
/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.