From: Krzysztof Kozlowski <krzk@kernel.org>
To: 1579567540@qq.com
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org, Vincent Mailhol <mailhol@kernel.org>,
kernel@pengutronix.de, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: can: rockchip: add rk3588v2 CAN-FD compatible
Date: Thu, 2 Jul 2026 09:43:16 +0200 [thread overview]
Message-ID: <20260702-quantum-hairy-quail-e3eee4@quoll> (raw)
In-Reply-To: <tencent_83A61C9A79199D04CC118A8026C435BFB907@qq.com>
On Wed, Jul 01, 2026 at 03:01:26PM +0800, 1579567540@qq.com wrote:
> From: luch00 <1579567540@qq.com>
>
> The RK3588 CAN-FD controller uses the same DT properties as the
> existing Rockchip CAN-FD blocks, so extend the current schema with a
DT properties have nothing to do here. Are you saying it is fully
compatible? Then express it properly with fallback.
> SoC-specific rockchip,rk3588v2-canfd compatible instead of creating a
> new binding file.
>
> Keep RK3588v2 as its own compatible rather than an rk3568v2 fallback.
Do not explain what you did. Explain WHY.
> Driver support uses separate match data and the RX FIFO count field
Driver is irrelevant here.
> layout differs from rk3568v2, so a dedicated compatible is the safer
> description.
>
> Signed-off-by: luch00 <1579567540@qq.com>
We do not take anonymous contributions.
> ---
> .../devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml b/Documentation/devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml
> index a077c0330..aa31ec78e 100644
> --- a/Documentation/devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml
> +++ b/Documentation/devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml
> @@ -17,6 +17,7 @@ properties:
> compatible:
> oneOf:
> - const: rockchip,rk3568v2-canfd
> + - const: rockchip,rk3588v2-canfd
So that's just enum with previous entry
And why is this different from rk3588?
> - items:
> - const: rockchip,rk3568v3-canfd
> - const: rockchip,rk3568v2-canfd
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-07-02 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260701070128.2096267-1-1579567540@qq.com>
2026-07-01 7:01 ` [PATCH 1/3] dt-bindings: can: rockchip: add rk3588v2 CAN-FD compatible 1579567540
2026-07-02 7:43 ` Krzysztof Kozlowski [this message]
2026-07-01 7:01 ` [PATCH 2/3] can: rockchip: add RK3588 CAN-FD support 1579567540
2026-07-01 9:55 ` Heiko Stübner
2026-07-01 11:07 ` Marc Kleine-Budde
2026-07-01 12:29 ` 💫.220
2026-07-01 16:02 ` Heiko Stübner
2026-07-01 7:01 ` [PATCH 3/3] arm64: dts: rockchip: add CAN-FD nodes for RK3588 1579567540
[not found] <tencent_97F21396469202221027FD429A6E69DA6409@qq.com>
2026-07-02 8:49 ` [PATCH 1/3] dt-bindings: can: rockchip: add rk3588v2 CAN-FD compatible 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=20260702-quantum-hairy-quail-e3eee4@quoll \
--to=krzk@kernel.org \
--cc=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=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