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 09:45:38 +0100 [thread overview]
Message-ID: <9c1b3e0b-84d8-4f1b-ba1b-233824d30c44@kernel.org> (raw)
In-Reply-To: <AS8PR04MB8642C9A1DA27CD0F3F51DF2287042@AS8PR04MB8642.eurprd04.prod.outlook.com>
On 17/12/2024 09:42, Jacky Bai wrote:
>> Subject: Re: [PATCH] arm64: dts: freescale: Add basic dtsi for imx943
>>
>> On Thu, Dec 12, 2024 at 05:35:55PM +0800, Jacky Bai wrote:
>>> The i.MX 943 applications processors integrate up to four Arm Cortex
>>> A55 cores and supports functional safety with built-in 2x Arm Cortex
>>> M33 and M7 cores which can be configured asa safety island. Optimizing
>>> performance and power efficiency for Industrial, IoT and automotive
>>> devices, i.MX 943 processors are built with NXP’s innovative Energy
>>> Flex architecture.
>>>
>>> This patch adds the minimal dtsi support for i.MX943 with peripherals
>>> like uart, edma, i2c, spi, mu, sai etc.
>>>
>>> Signed-off-by: Jacky Bai <ping.bai@nxp.com>
>>> ---
>>> arch/arm64/boot/dts/freescale/imx943-clock.h | 196 +++
>>> .../arm64/boot/dts/freescale/imx943-pinfunc.h | 1542
>> +++++++++++++++++
>>> arch/arm64/boot/dts/freescale/imx943-power.h | 41 +
>>> arch/arm64/boot/dts/freescale/imx943.dtsi | 1284
>> ++++++++++++++
>>> 4 files changed, 3063 insertions(+)
>>> create mode 100644 arch/arm64/boot/dts/freescale/imx943-clock.h
>>> create mode 100644 arch/arm64/boot/dts/freescale/imx943-pinfunc.h
>>> create mode 100644 arch/arm64/boot/dts/freescale/imx943-power.h
>>> create mode 100644 arch/arm64/boot/dts/freescale/imx943.dtsi
>>>
>>> diff --git a/arch/arm64/boot/dts/freescale/imx943-clock.h
>>> b/arch/arm64/boot/dts/freescale/imx943-clock.h
>>> new file mode 100644
>>> index 000000000000..64b9d5d4051e
>>> --- /dev/null
>>> +++ b/arch/arm64/boot/dts/freescale/imx943-clock.h
>>> @@ -0,0 +1,196 @@
>>> +/* SPDX-License-Identifier: GPL-2.0-only OR MIT */
>>> +/*
>>> + * Copyright 2024 NXP
>>> + */
>>> +
>>> +#ifndef __CLOCK_IMX943_H
>>> +#define __CLOCK_IMX943_H
>>> +
>>> +#define IMX943_CLK_EXT 0
>>> +#define IMX943_CLK_OSC32K 1
>>> +#define IMX943_CLK_OSC24M 2
>>
>>
>> Why exactly are you adding clock indices to header files? Nothing in commit
>> msg explains that.
>
> These clock index macro defines will be used in dtsi or dts for clock reference.
> I just follow the way that we have done for i.MX95. Anything need to be improved or refined?
> For commit msg, I will add some explains in v2.
It is fine, just unexpected, so you have entire commit msg to explain this.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-17 8:45 UTC|newest]
Thread overview: 13+ 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
2024-12-12 9:35 ` [PATCH] arm64: dts: freescale: Add basic dtsi for imx943 Jacky Bai
2024-12-12 16:48 ` Frank Li
2024-12-17 8:23 ` Jacky Bai
2024-12-16 10:15 ` Krzysztof Kozlowski
2024-12-17 8:42 ` Jacky Bai
2024-12-17 8:45 ` Krzysztof Kozlowski [this message]
2024-12-16 10:17 ` Krzysztof Kozlowski
2024-12-17 8:55 ` Jacky Bai
2024-12-17 9:03 ` Krzysztof Kozlowski
2024-12-17 9:47 ` Jacky Bai
2024-12-16 10:19 ` Krzysztof Kozlowski
2024-12-17 9:02 ` 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=9c1b3e0b-84d8-4f1b-ba1b-233824d30c44@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