From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Michael Walle <michael@walle.cc>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-can@vger.kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH v2 1/3] dt-bindings: can: flexcan: list supported processors
Date: Tue, 6 Oct 2020 21:25:09 +0200 [thread overview]
Message-ID: <afdcecef-10c6-738b-29fe-09353d1c7c92@pengutronix.de> (raw)
In-Reply-To: <20201001091131.30514-2-michael@walle.cc>
[-- Attachment #1.1: Type: text/plain, Size: 1530 bytes --]
On 10/1/20 11:11 AM, Michael Walle wrote:
> The compatible is a pattern match. Explicitly list all possible values.
> Also mention that the ls1028ar1 must be followed by lx2160ar1.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> Documentation/devicetree/bindings/net/can/fsl-flexcan.txt | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt b/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
> index 94c0f8bf4deb..c6152dc2d2d0 100644
> --- a/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
> +++ b/Documentation/devicetree/bindings/net/can/fsl-flexcan.txt
> @@ -4,6 +4,12 @@ Required properties:
>
> - compatible : Should be "fsl,<processor>-flexcan"
>
> + where <processor> is imx8qm, imx6q, imx28, imx53, imx35, imx25, p1010,
> + vf610, ls1021ar2, lx2160ar1, ls1028ar1.
> +
> + The ls1028ar1 must be followed by lx2160ar1, e.g.
> + - "fsl,ls1028ar1-flexcan", "fsl,lx2160ar1-flexcan"
> +
> An implementation should also claim any of the following compatibles
> that it is fully backwards compatible with:
>
>
Added this patch to linux-can-next. The others should probably go via the arm
SoC tree.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-06 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 9:11 [PATCH v2 0/3] arm64: dts: add FlexCAN support to LS1028A and sl28 Michael Walle
2020-10-01 9:11 ` [PATCH v2 1/3] dt-bindings: can: flexcan: list supported processors Michael Walle
2020-10-06 19:25 ` Marc Kleine-Budde [this message]
2020-10-01 9:11 ` [PATCH v2 2/3] arm64: dts: ls1028a: add missing CAN nodes Michael Walle
2020-10-28 9:06 ` Shawn Guo
2020-10-01 9:11 ` [PATCH v2 3/3] arm64: dts: freescale: sl28: add CAN node Michael Walle
2020-10-28 9:06 ` Shawn Guo
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=afdcecef-10c6-738b-29fe-09353d1c7c92@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=o.rempel@pengutronix.de \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).