From: Daniel Baluta <daniel.baluta@oss.nxp.com>
To: Shengjiu Wang <shengjiu.wang@nxp.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Frank.Li@nxp.com, s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] arm64: dts: imx952: Add audio device nodes
Date: Thu, 12 Mar 2026 08:40:56 +0200 [thread overview]
Message-ID: <af948fb4-4f63-4276-9368-9d41e80c3e7c@oss.nxp.com> (raw)
In-Reply-To: <20260312034912.4007057-2-shengjiu.wang@nxp.com>
On 3/12/26 05:49, Shengjiu Wang wrote:
> Add audio device nodes, include SAI, MICFIL, ASRC, Audio Mixer.
>
> Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx952.dtsi | 199 ++++++++++++++++++++++
> 1 file changed, 199 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx952.dtsi b/arch/arm64/boot/dts/freescale/imx952.dtsi
> index 0f86b5626cdd..5787c12e788f 100644
> --- a/arch/arm64/boot/dts/freescale/imx952.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx952.dtsi
> @@ -823,6 +823,156 @@ usdhc3: mmc@42c40000 {
> };
> };
>
> + aips5: bus@43000000 {
> + compatible = "fsl,aips-bus", "simple-bus";
> + reg = <0 0x43000000 0 0x800000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x43000000 0x0 0x43000000 0x800000>;
> +
> + asrc1: asrc@43000000 {
> + compatible = "fsl,imx952-asrc";
> + reg = <0x43000000 0x10000>;
> + interrupts = <GIC_SPI 376 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&scmi_clk IMX952_CLK_BUSWAKEUP>,
> + <&scmi_clk IMX952_CLK_BUSWAKEUP>,
> + <&scmi_clk IMX952_CLK_ASRC1>,
> + <&scmi_clk IMX952_CLK_ASRC2>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>,
> + <&clk_dummy>;
> + clock-names = "mem", "ipg",
> + "asrck_0", "asrck_1", "asrck_2", "asrck_3",
> + "asrck_4", "asrck_5", "asrck_6", "asrck_7",
> + "asrck_8", "asrck_9", "asrck_a", "asrck_b",
> + "asrck_c", "asrck_d", "asrck_e", "asrck_f",
> + "spba";
> + dmas = <&edma2 97 0 0>, <&edma2 98 0 0>, <&edma2 99 0 0>,
> + <&edma2 100 0 1>, <&edma2 101 0 1>, <&edma2 102 0 1>;
For consistency we should use symbolic macros for directions like you did below.
Use FSL_EDMA_RX for rx direction and also introduce FSL_EDMA_TX for tx direction.
> + dma-names = "rxa", "rxb", "rxc",
> + "txa", "txb", "txc";
> + #sound-dai-cells = <0>;
> + fsl,asrc-rate = <8000>;
> + fsl,asrc-width = <16>;
> + status = "disabled";
> + };
[...]
> + sai3: sai@433e0000 {
> + compatible = "fsl,imx952-sai", "fsl,imx95-sai";
> + reg = <0x433e0000 0x10000>;
> + interrupts = <GIC_SPI 170 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&scmi_clk IMX952_CLK_BUSWAKEUP>, <&clk_dummy>,
> + <&scmi_clk IMX952_CLK_SAI3>, <&clk_dummy>,
> + <&clk_dummy>;
> + clock-names = "bus", "mclk0", "mclk1", "mclk2", "mclk3";
> + dmas = <&edma2 61 0 FSL_EDMA_RX>, <&edma2 60 0 0>;
As I said we should introduce FSL_EDMA_TX and this will read as:
dmas = <&edma2 61 0 FSL_EDMA_RX>, <&edma2 60 0 FSL_EDMA_TX>;
Otherwise, looks good to me.
next prev parent reply other threads:[~2026-03-12 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 3:49 [PATCH 0/4] arm64: dts: imx952-evk: Add audio sound cards Shengjiu Wang
2026-03-12 3:49 ` [PATCH 1/4] arm64: dts: imx952: Add audio device nodes Shengjiu Wang
2026-03-12 6:40 ` Daniel Baluta [this message]
2026-03-12 6:54 ` Shengjiu Wang
2026-03-12 7:13 ` Daniel Baluta
2026-03-12 9:53 ` Shengjiu Wang
2026-03-12 3:49 ` [PATCH 2/4] arm64: dts: imx952-evk: Add sound-wm8962 support Shengjiu Wang
2026-03-12 6:51 ` Daniel Baluta
2026-03-12 9:43 ` Alexander Stein
2026-03-12 9:49 ` Shengjiu Wang
2026-03-12 3:49 ` [PATCH 3/4] arm64: dts: imx952-evk: Add bt-sco sound card support Shengjiu Wang
2026-03-12 6:50 ` Daniel Baluta
2026-03-12 3:49 ` [PATCH 4/4] arm64: dts: imx952-evk: Add PDM microphone " Shengjiu Wang
2026-03-12 6:49 ` Daniel Baluta
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=af948fb4-4f63-4276-9368-9d41e80c3e7c@oss.nxp.com \
--to=daniel.baluta@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shengjiu.wang@nxp.com \
/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