From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jacky Bai <ping.bai@nxp.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, aisheng.dong@nxp.com,
peng.fan@nxp.com, frank.li@nxp.com
Subject: Re: [PATCH v2 3/4] arm64: dts: freescale: Add basic dtsi for imx943
Date: Tue, 4 Mar 2025 15:54:10 +0100 [thread overview]
Message-ID: <9581e376-19b2-4d4e-ad81-cc24e39e9d33@kernel.org> (raw)
In-Reply-To: <20250304093127.1954549-4-ping.bai@nxp.com>
On 04/03/2025 10:31, Jacky Bai wrote:
> Add the minimal dtsi support for i.MX943. i.MX943 is the
> first SoC of i.MX94 Family, create a common dtsi for the
> whole i.MX94 family, and the specific dtsi part for i.MX943.
>
> The clock, power domain and perf index need to be used by
> the device nodes for resource reference, add them along
> with the dtsi support.
>
> Signed-off-by: Jacky Bai <ping.bai@nxp.com>
> ---
> - v2 changes:
> - remove the unnecessary macro define in clock header as suggested by Krzysztof
> - split the dtsi into imx94.dtsi and imx943.dtsi
> - use low case in the pinfunc header as Frank suggested
> - reorder the device nodes and properties
> - resolve Krzysztof's other comments
Which ones? Be specific.
Based on last issue, I don't think you implemented comments.
> +
> + a55_irqsteer: interrupt-controller@446a0000 {
> + compatible = "fsl,imx-irqsteer";
> + reg = <0x446a0000 0x1000>;
> + #interrupt-cells = <1>;
> + interrupt-controller;
> + interrupts = <GIC_SPI 224 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 225 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 226 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 227 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 228 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 229 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&scmi_clk IMX94_CLK_BUSAON>;
> + clock-names = "ipg";
> + fsl,channel = <0>;
> + fsl,num-irqs = <960>;
> + };
> + };
> +
> + aips4: bus@49000000 {
> + compatible = "fsl,aips-bus", "simple-bus";
> + reg = <0x0 0x49000000 0x0 0x800000>;
> + ranges = <0x49000000 0x0 0x49000000 0x800000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + wdog3: watchdog@49220000 {
> + compatible = "fsl,imx93-wdt";
imx93 or imx95, like in other places? And the commit msg says imx943.
I already asked for that.
> + reg = <0x49220000 0x10000>;
> + interrupts = <GIC_SPI 90 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&scmi_clk IMX94_CLK_BUSWAKEUP>;
> + timeout-sec = <40>;
> + fsl,ext-reset-output;
> + status = "disabled";
> + };
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-04 15:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 9:31 [PATCH v2 0/4] Add i.MX943 basic dts support Jacky Bai
2025-03-04 9:31 ` [PATCH v2 1/4] dt-bindings: dma: fsl-edma: add interrupts-extended property Jacky Bai
2025-03-04 10:57 ` Rob Herring (Arm)
2025-03-04 13:13 ` Rob Herring
2025-03-04 14:40 ` Jacky Bai
2025-03-04 14:50 ` Krzysztof Kozlowski
2025-03-04 14:53 ` Rob Herring
2025-03-04 15:38 ` Jacky Bai
2025-03-04 15:26 ` Frank Li
2025-03-04 15:41 ` Jacky Bai
2025-03-04 9:31 ` [PATCH v2 2/4] dt-bindings: arm: fsl: add i.MX943 EVK board Jacky Bai
2025-03-04 14:55 ` Krzysztof Kozlowski
2025-03-04 9:31 ` [PATCH v2 4/4] arm64: dts: freescale: Add minimal dts support for imx943 evk Jacky Bai
2025-03-04 15:27 ` Frank Li
[not found] ` <20250304093127.1954549-4-ping.bai@nxp.com>
2025-03-04 14:54 ` Krzysztof Kozlowski [this message]
2025-03-04 15:16 ` [PATCH v2 3/4] arm64: dts: freescale: Add basic dtsi for imx943 Jacky Bai
2025-03-05 1:22 ` Jacky Bai
2025-03-04 15:35 ` Frank Li
2025-03-05 0:34 ` 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=9581e376-19b2-4d4e-ad81-cc24e39e9d33@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).