Linux CAN drivers development
 help / color / mirror / Atom feed
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: fsl,mpc5xxx-mscan: Convert to DT schema
Date: Mon, 14 Sep 2026 09:31:04 +0200	[thread overview]
Message-ID: <a3d4cb8f-3550-48de-a275-914c4aef2923@kernel.org> (raw)
In-Reply-To: <20260914055608.495084-2-quchaosheng000406@163.com>

On 14/09/2026 07:56, Quchaosheng wrote:
> Convert the Freescale MPC5xxx MSCAN controller binding from free-form
> text to DT schema, and reference the common can-controller.yaml schema.
> 
> The original text described the two compatible strings and their clock
> source properties in separate sections. "fsl,mpc5200b-mscan" is added as
> a fallback of "fsl,mpc5200-mscan", the way existing device trees such as
> mpc5200b.dtsi use it. The allowed values of fsl,mscan-clock-source are
> constrained to the strings the driver accepts: the driver compares
> against "ip", "sys" and "ref" and rejects anything else.
> 
> The clocks and clock-names properties are documented as well. The driver

Don't paste here LLM output.

> looks up the "ipg", "ips", "sys", "ref" and "mclk" clocks by name, and
> the existing MPC5121 device trees provide exactly those. They were not
> described by the old text.

You write complicated paragraphs and complicated sentences in some
passive voice. Please look at other commits how the commit msg is written.

> 
> The note that the MPC5121 Rev. 1 processor is not supported is kept from
> the original text.
> 
> unevaluatedProperties is used rather than additionalProperties so that
> properties provided by can-controller.yaml remain usable.

Same problems.

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


Best regards,
Krzysztof

  parent reply	other threads:[~2026-09-14  7:31 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 [this message]
2026-09-14  8:49     ` Krzysztof Kozlowski
2026-09-14  7:23 ` [PATCH v2] dt-bindings: net: can: holt,hi3110: " 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=a3d4cb8f-3550-48de-a275-914c4aef2923@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