From: Krzysztof Kozlowski <krzk@kernel.org>
To: Quchaosheng <quchaosheng000406@163.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-can@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5] dt-bindings: net: can: convert ifi_canfd to DT schema
Date: Tue, 15 Sep 2026 13:00:10 +0200 [thread overview]
Message-ID: <70ae05a5-2415-4895-bc64-37b3d3ba54ac@kernel.org> (raw)
In-Reply-To: <20260914022145.408976-1-quchaosheng000406@163.com>
On 14/09/2026 04:21, Quchaosheng wrote:
> Convert the IFI CAN-FD controller binding from free-form text to DT
> schema, and reference the common can-controller.yaml schema.
>
> The driver matches on the "ifi,canfd-1.0" compatible and obtains its
> interrupt through platform_get_irq(), so interrupts is required.
>
> The example uses the GIC and irq header defines instead of the raw
> numbers from the original text, which keeps the values unchanged
> (GIC_SPI is 0, IRQ_TYPE_NONE is 0 and 1 is IRQ_TYPE_EDGE_RISING). The
> node name is changed from "canfd" to "can" so that it matches the
> $nodename pattern required by can-controller.yaml.
>
> ---
> v2:
> - Correct the description: this is a soft IP block typically synthesised
> into an FPGA or CPLD, not a controller found on Renesas SoCs.
> Wording now follows the driver's Kconfig entry.
>
> v3:
> - Use unevaluatedProperties: false instead of additionalProperties: false.
> As can-controller.yaml is referenced through allOf, additionalProperties
> would have rejected properties defined by that common schema, such as
> termination-gpios and termination-ohms.
>
> v4:
> - Use defines instead of raw numbers in the example, and rename the
> example node from canfd to can. No functional change.
>
> v5:
> - Re-send the patch on its own. The v4 posting accidentally included
> unrelated changes to the xilinx-xadc binding and did not remove
> ifi_canfd.txt. Only the intended change is present now.
You send this way too many times. Please slow down.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-15 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 2:21 [PATCH v5] dt-bindings: net: can: convert ifi_canfd to DT schema Quchaosheng
2026-09-15 11:00 ` Krzysztof Kozlowski [this message]
2026-09-17 9:20 ` Quchaosheng
2026-09-17 13:41 ` Conor
2026-09-22 6:19 ` Quchaosheng
2026-09-22 7:06 ` Quchaosheng
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=70ae05a5-2415-4895-bc64-37b3d3ba54ac@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=quchaosheng000406@163.com \
--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