From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Zi-Yu Chen <zychennvt@gmail.com>
Cc: arnd@arndb.de, olof@lixom.net, soc@lists.linux.dev,
ychuang3@nuvoton.com, schung@nuvoton.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] arm64: dts: nuvoton: ma35d1: add CAN nodes
Date: Mon, 24 Aug 2026 12:39:52 +0200 [thread overview]
Message-ID: <20260824-smooth-jolly-sponge-ba4b95-mkl@pengutronix.de> (raw)
In-Reply-To: <20260708082457.460710-1-zychennvt@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On 08.07.2026 16:24:57, Zi-Yu Chen wrote:
> Add controller nodes for the four Bosch M_CAN blocks found on the
> Nuvoton MA35D1 SoC.
>
> Additionally, configure pinctrl and enable CAN1 and CAN3 on the
> MA35D1 SOM board. Also, update the APLL frequency to 200MHz to ensure
> the CAN controllers receive the required input clock for 50MHz operation.
50 MHz is an unusual CAN clock frequency. Better use a multiple of 40
MHz. Within the limits of the m_can IP core, the higher the multiple the
better.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-24 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 8:24 [PATCH v2 RESEND] arm64: dts: nuvoton: ma35d1: add CAN nodes Zi-Yu Chen
2026-07-10 14:16 ` Arnd Bergmann
2026-07-13 2:57 ` Jacky Huang
2026-08-04 5:13 ` Andrew Jeffery
2026-08-04 7:41 ` Arnd Bergmann
2026-08-24 10:39 ` Marc Kleine-Budde [this message]
2026-09-08 1:47 ` zychen
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=20260824-smooth-jolly-sponge-ba4b95-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=schung@nuvoton.com \
--cc=soc@lists.linux.dev \
--cc=ychuang3@nuvoton.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox