From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jacky Bai <ping.bai@nxp.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Aisheng Dong <aisheng.dong@nxp.com>, Peng Fan <peng.fan@nxp.com>,
Frank Li <frank.li@nxp.com>
Subject: Re: [PATCH] arm64: dts: freescale: Add basic dtsi for imx943
Date: Tue, 17 Dec 2024 10:03:18 +0100 [thread overview]
Message-ID: <fa130432-bbfe-4d8f-913c-e86488efe203@kernel.org> (raw)
In-Reply-To: <AS8PR04MB8642D11477A37E75BAB71F3087042@AS8PR04MB8642.eurprd04.prod.outlook.com>
On 17/12/2024 09:55, Jacky Bai wrote:
>>
>>> + device_type = "cpu";
>
> ...
>
>>> + edma2: dma-controller@42000000 {
>>> + compatible = "fsl,imx95-edma5";
>>
>> imx943 or imx95?
>>
>
> Compatible with imx95, so I did not add new redundant dt binding entry.
The entry is not redundant, because allows handling quirks or missing
features (see writing bindings).
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-17 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 9:35 [PATCH 0/1] Add i.MX943 basic dtsi support Jacky Bai
[not found] ` <20241212093555.1376568-2-ping.bai@nxp.com>
2024-12-16 10:15 ` [PATCH] arm64: dts: freescale: Add basic dtsi for imx943 Krzysztof Kozlowski
2024-12-17 8:42 ` Jacky Bai
2024-12-17 8:45 ` Krzysztof Kozlowski
2024-12-16 10:17 ` Krzysztof Kozlowski
2024-12-17 8:55 ` Jacky Bai
2024-12-17 9:03 ` Krzysztof Kozlowski [this message]
2024-12-17 9:47 ` Jacky Bai
2024-12-16 10:19 ` Krzysztof Kozlowski
2024-12-17 9:02 ` Jacky Bai
[not found] ` <Z1sT8FQXnxyZUeo3@lizhi-Precision-Tower-5810>
2024-12-17 8:23 ` Jacky Bai
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=fa130432-bbfe-4d8f-913c-e86488efe203@kernel.org \
--to=krzk@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peng.fan@nxp.com \
--cc=ping.bai@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--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).