From: Daniel Baluta <daniel.baluta@nxp.com>
To: shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
festevam@gmail.com, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, frank.li@nxp.com,
aisheng.dong@nxp.com, daniel.baluta@gmail.com,
laurentiu.mihalcea@nxp.com, shengjiu.wang@nxp.com,
iuliana.prodan@nxp.com, Daniel Baluta <daniel.baluta@nxp.com>
Subject: [PATCH 5/5] arm64: dts: Add dsp rproc related mem regions
Date: Wed, 20 Nov 2024 15:58:58 +0200 [thread overview]
Message-ID: <20241120135859.3133984-6-daniel.baluta@nxp.com> (raw)
In-Reply-To: <20241120135859.3133984-1-daniel.baluta@nxp.com>
With imx8mp-evk board we are now configuring 'dsp' node for rproc usage,
so add rproc specific memory regions.
Also, enable dsp node because it is ready to be used.
Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
---
arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 6 ++++++
arch/arm64/boot/dts/freescale/imx8mp.dtsi | 1 -
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8mp-evk.dts b/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
index d26930f1a9e9..adb01a484d78 100644
--- a/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
+++ b/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
@@ -291,6 +291,12 @@ &aud2htx {
status = "okay";
};
+&dsp {
+ memory-region = <&dsp_vdev0buffer>, <&dsp_vdev0vring0>,
+ <&dsp_vdev0vring1>, <&dsp_reserved>;
+ status = "okay";
+};
+
&eqos {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_eqos>;
diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
index fa4ff75af12d..e6f3ac02689c 100644
--- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
@@ -282,7 +282,6 @@ reserved-memory {
dsp_reserved: dsp@92400000 {
reg = <0 0x92400000 0 0x1000000>;
no-map;
- status = "disabled";
};
};
--
2.43.0
next prev parent reply other threads:[~2024-11-20 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 13:58 [PATCH 0/5] Configure imx8mp dsp node for rproc usage Daniel Baluta
2024-11-20 13:58 ` [PATCH 1/5] arm64: dts: imx8mp: Add mu2 root clock Daniel Baluta
2024-11-20 13:58 ` [PATCH 2/5] arm64: dts: imx8mp: Configure dsp node for rproc usage Daniel Baluta
2024-11-20 13:58 ` [PATCH 3/5] arm64: dts: imx8mp: Add DSP clocks Daniel Baluta
2024-11-20 13:58 ` [PATCH 4/5] arm64: dts: imx8mp: Add fsl,dsp-ctrl property for dsp Daniel Baluta
2024-11-21 11:33 ` Peng Fan
2024-11-21 11:48 ` Daniel Baluta
2024-11-20 13:58 ` Daniel Baluta [this message]
2024-11-20 15:36 ` [PATCH 5/5] arm64: dts: Add dsp rproc related mem regions Ahmad Fatoum
2024-11-20 15:40 ` Daniel Baluta
2024-11-20 16:02 ` [PATCH 0/5] Configure imx8mp dsp node for rproc usage Rob Herring (Arm)
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=20241120135859.3133984-6-daniel.baluta@nxp.com \
--to=daniel.baluta@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=iuliana.prodan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=laurentiu.mihalcea@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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
all inboxes | Powered by JetHome®