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 v2] dt-bindings: net: can: holt,hi3110: Convert to DT schema
Date: Mon, 14 Sep 2026 09:23:55 +0200 [thread overview]
Message-ID: <63126241-b217-46c6-8ec3-071283e86d69@kernel.org> (raw)
In-Reply-To: <20260914055608.495084-1-quchaosheng000406@163.com>
On 14/09/2026 07:56, Quchaosheng wrote:
> Convert the Holt HI-311X stand-alone CAN controller binding from
> free-form text to DT schema, and reference the common can-controller.yaml
> schema.
>
Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830
> The controller is connected over SPI, so reference
> spi-peripheral-props.yaml as well, otherwise the standard SPI properties
> such as spi-max-frequency would be rejected by unevaluatedProperties.
Redundant, drop.
>
> The old text listed clocks as required, but the driver obtains the clock
> with devm_clk_get_optional() and falls back to the "clock-frequency"
No, read the git log history. It's only for ACPI. You cannot add ABI
post factum on the basis of "but someone added it to the driver code".
> property when no clock is provided, so either one of the two must be
> present and neither is required on its own. This is expressed with an
> anyOf block, and clock-frequency is documented, as it was previously
> undocumented. The maximum supported clock frequency of 40000000 is
> enforced, as that is the limit the driver applies.
>
> unevaluatedProperties is used rather than additionalProperties so that
> properties provided by can-controller.yaml remain usable.
All this is redundant. You just paste here LLM explanations, so let me
stop you right here - do not ever paste us LLM text. It's pointless.
Explain the changes done to the binding ONLY.
>
> Signed-off-by: Quchaosheng <quchaosheng000406@163.com>
> ---
> v2:
> - Reference spi-peripheral-props.yaml. Without it, unevaluatedProperties
> rejected the standard SPI properties, spi-max-frequency among them.
> Reported by Sashiko.
>
> - Add a maximum of 40000000 to clock-frequency. The description stated
> the limit but did not enforce it. Reported by Sashiko.
> ---
> .../bindings/net/can/holt,hi311x.yaml | 81 +++++++++++++++++++
> .../bindings/net/can/holt_hi311x.txt | 23 ------
> 2 files changed, 81 insertions(+), 23 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/can/holt,hi311x.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/can/holt_hi311x.txt
>
> diff --git a/Documentation/devicetree/bindings/net/can/holt,hi311x.yaml b/Documentation/devicetree/bindings/net/can/holt,hi311x.yaml
> new file mode 100644
> index 000000000..36497b114
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/can/holt,hi311x.yaml
> @@ -0,0 +1,81 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/can/holt,hi311x.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Holt HI-311X stand-alone CAN controller
> +
> +maintainers:
> + - Marc Kleine-Budde <mkl@pengutronix.de>
> +
> +description:
> + The Holt HI-3110 is a stand-alone CAN controller with an SPI interface.
> +
> +allOf:
> + - $ref: can-controller.yaml#
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +properties:
> + compatible:
> + const: holt,hi3110
> +
> + reg:
> + description: SPI chip select.
> + maxItems: 1
> +
> + clocks:
> + description:
> + The clock feeding the CAN controller. If this property is not present
> + clock-frequency must be specified instead.
> + maxItems: 1
> +
> + clock-frequency:
> + description:
> + Frequency of the clock feeding the CAN controller, in Hz. Used when
> + no clocks property is provided.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 40000000
No
> +
> + interrupts:
> + description: IRQ line for the CAN controller.
> + maxItems: 1
> +
> + vdd-supply:
> + description: Regulator that powers the CAN controller.
> +
> + xceiver-supply:
> + description: Regulator that powers the CAN transceiver.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +anyOf:
> + - required:
> + - clocks
> + - required:
> + - clock-frequency
No
Best regards,
Krzysztof
prev parent reply other threads:[~2026-09-14 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 5:56 [PATCH v2] dt-bindings: net: can: holt,hi3110: Convert to DT schema Quchaosheng
2026-09-14 5:56 ` [PATCH v2] dt-bindings: net: can: fsl,mpc5xxx-mscan: " Quchaosheng
2026-09-14 6:03 ` sashiko-bot
2026-09-14 7:31 ` Krzysztof Kozlowski
2026-09-14 8:49 ` Krzysztof Kozlowski
2026-09-14 7:23 ` Krzysztof Kozlowski [this message]
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=63126241-b217-46c6-8ec3-071283e86d69@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