From: Krzysztof Kozlowski <krzk@kernel.org>
To: Elaine Zhang <zhangqing@rock-chips.com>,
mkl@pengutronix.de, kernel@pengutronix.de,
mailhol.vincent@wanadoo.fr, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, heiko@sntech.de, cl@rock-chips.com,
kever.yang@rock-chips.com
Cc: linux-can@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: can: rockchip_canfd: add rk3576 CAN-FD controller
Date: Thu, 22 May 2025 08:58:16 +0200 [thread overview]
Message-ID: <ed51c57a-35c4-43e4-9041-221026fb6273@kernel.org> (raw)
In-Reply-To: <20250522063232.2197432-2-zhangqing@rock-chips.com>
On 22/05/2025 08:32, Elaine Zhang wrote:
> Add documentation for the rockchip rk3576 CAN-FD controller.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> ---
> .../net/can/rockchip,rk3576-canfd.yaml | 82 +++++++++++++++++++
> 1 file changed, 82 insertions(+)
There is no cover letter (maybe something got lost on the lists?), no
changelog. What was happening with this patch?
> create mode 100644 Documentation/devicetree/bindings/net/can/rockchip,rk3576-canfd.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/can/rockchip,rk3576-canfd.yaml b/Documentation/devicetree/bindings/net/can/rockchip,rk3576-canfd.yaml
> new file mode 100644
> index 000000000000..85caf6d19607
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/can/rockchip,rk3576-canfd.yaml
> @@ -0,0 +1,82 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/can/rockchip,rk3568v2-canfd.yaml#
Never tested, so just quick glance, not review.
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title:
That's never a line break. Open existing files and look how it is done
there.
> + Rk3576 CAN-FD controller
...
> +
> + can0: can@2ac00000 {
Drop label
> + compatible = "rockchip,rk3576-canfd";
Messed indentation
> + reg = <0x0 0x2ac00000 0x0 0x1000>;
> + interrupts = <GIC_SPI 121 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru CLK_CAN0>, <&cru HCLK_CAN0>;
> + clock-names = "baud", "pclk";
> + resets = <&cru SRST_CAN0>, <&cru SRST_H_CAN0>;
> + reset-names = "can", "can-apb";
> + dmas = <&dmac0 20>;
> + dma-names = "rx";
> + status = "disabled";
No, it cannot be disabled. Drop. Look at other bindings or example-schema.
> + };
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-22 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 6:32 [PATCH v3 0/2] rockchip: add can for RK3576 Soc Elaine Zhang
2025-05-22 6:32 ` [PATCH v3 1/3] dt-bindings: can: rockchip_canfd: add rk3576 CAN-FD controller Elaine Zhang
2025-05-22 6:58 ` Krzysztof Kozlowski [this message]
2025-05-22 6:32 ` [PATCH v3 2/3] net: can: rockchip: add can for RK3576 Soc Elaine Zhang
2025-05-22 7:00 ` Krzysztof Kozlowski
2025-05-22 7:51 ` Vincent Mailhol
2025-05-22 7:59 ` Marc Kleine-Budde
2025-05-22 6:32 ` [PATCH v3 3/3] arm64: dts: rockchip: rk3576: add can dts nodes Elaine Zhang
2025-05-22 9:02 ` 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=ed51c57a-35c4-43e4-9041-221026fb6273@kernel.org \
--to=krzk@kernel.org \
--cc=cl@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@pengutronix.de \
--cc=kever.yang@rock-chips.com \
--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.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
--cc=zhangqing@rock-chips.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
all inboxes | Powered by JetHome®