Devicetree
 help / color / mirror / Atom feed
From: "Cunhao Lu" <1579567540@qq.com>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>
Cc: krzk <krzk@kernel.org>, heiko <heiko@sntech.de>,
	linux-can <linux-can@vger.kernel.org>,
	mailhol <mailhol@kernel.org>, kernel <kernel@pengutronix.de>,
	robh <robh@kernel.org>, krzk+dt <krzk+dt@kernel.org>,
	conor+dt <conor+dt@kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-rockchip <linux-rockchip@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] dt-bindings: can: rockchip: add rk3588v2 CAN-FD compatible
Date: Thu, 2 Jul 2026 16:57:46 +0800	[thread overview]
Message-ID: <tencent_F173D3200DB38C5942E848728028E291DF06@qq.com> (raw)

Hi Marc,

thanks for the explanation.

> However, the version register _in_ the CAN-FD was not changed. :/
> This is why we have a rockchip,rk3568v2-canfd and a
> rockchip,rk3568v3-canfd compatible.
>
> Yes, please use rockchip,rk3588-canfd, unless we get information from
> rockchips about CAN-FD errata and SoC silicon revisions.

Understood. I changed the v2 series to use rockchip,rk3588-canfd
instead of rockchip,rk3588v2-canfd.

This includes the binding, the RK3588 DTS nodes, the driver OF match,
and the internal driver model name.

Thanks,
Cunhao Lu

             reply	other threads:[~2026-07-02  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  8:57 Cunhao Lu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-02  8:17 [PATCH 1/3] dt-bindings: can: rockchip: add rk3588v2 CAN-FD compatible Cunhao Lu
2026-07-02  8:49 ` Marc Kleine-Budde
     [not found] <20260701070128.2096267-1-1579567540@qq.com>
2026-07-01  7:01 ` 1579567540
2026-07-02  7:43   ` Krzysztof Kozlowski

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=tencent_F173D3200DB38C5942E848728028E291DF06@qq.com \
    --to=1579567540@qq.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --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=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