From: "Heiko Stübner" <heiko@sntech.de>
To: Cunhao Lu <1579567540@qq.com>, Marc Kleine-Budde <mkl@pengutronix.de>
Cc: kernel@pengutronix.de, Vincent Mailhol <mailhol@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-can@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Heiko Stuebner <heiko.stuebner@cherry.de>,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH v6 0/4] can: rockchip: add RK3588 CAN support
Date: Mon, 17 Aug 2026 18:25:02 +0200 [thread overview]
Message-ID: <6011470.tIAgqjz4sF@diego> (raw)
In-Reply-To: <20260817-guillemot-of-premium-saturation-6b893d-mkl@pengutronix.de>
Am Montag, 17. August 2026, 18:23:03 Mitteleuropäische Sommerzeit schrieb Marc Kleine-Budde:
> On 30.07.2026 22:34:01, Cunhao Lu wrote:
> > Add support for the RK3588 CAN controller.
> >
> > RK3588 integrates three CAN-FD controllers that are closely related to
> > the existing Rockchip CAN-FD IP already supported in the kernel. The
> > RK3588 variant is not fully compatible with RK3568v2 because the RX
> > FIFO count register field has a different layout.
> >
> > This series therefore:
> >
> > - extends the existing Rockchip CAN-FD binding with the
> > rockchip,rk3588-canfd compatible
> > - adds a dedicated RK3588 match entry and devtype in the driver
>
> I'll take the first 2 patches.
>
> > - describes the three CAN controller nodes in rk3588-base.dtsi
> > - enables CAN on the RK3588 Tiger Haikou board
>
> The DT changes should probably go via the rockchip tree.
yep :-) .
I'll pick those up after the merge-window.
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-08-17 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 14:34 [PATCH v6 0/4] can: rockchip: add RK3588 CAN support Cunhao Lu
2026-08-17 16:23 ` Marc Kleine-Budde
2026-08-17 16:25 ` Heiko Stübner [this message]
[not found] <20260730-master-v6-0-dfb63e234775@qq.com>
2026-07-30 14:34 ` [PATCH v6 1/4] dt-bindings: can: rockchip: add rk3588 CAN-FD compatible Cunhao Lu
2026-07-30 14:34 ` [PATCH v6 2/4] can: rockchip: add RK3588 CAN support Cunhao Lu
2026-07-31 7:18 ` Marc Kleine-Budde
2026-07-31 9:23 ` Cunhao Lu
2026-07-31 10:35 ` Marc Kleine-Budde
2026-07-31 13:17 ` Cunhao Lu
2026-08-11 15:05 ` Cunhao Lu
2026-07-30 14:34 ` [PATCH v6 3/4] arm64: dts: rockchip: add CAN-FD nodes for RK3588 Cunhao Lu
2026-07-30 14:34 ` [PATCH v6 4/4] arm64: dts: rockchip: Enable CAN controller on RK3588-Tiger-Haikou Cunhao Lu
2026-07-30 15:21 ` Quentin Schulz
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=6011470.tIAgqjz4sF@diego \
--to=heiko@sntech.de \
--cc=1579567540@qq.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko.stuebner@cherry.de \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=quentin.schulz@cherry.de \
--cc=robh@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