From: Daniel Baluta <daniel.baluta@nxp.com>
To: shawnguo@kernel.org, robh@kernel.org
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
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, a.fatoum@pengutronix.de,
mathieu.poirier@linaro.org, linux-remoteproc@vger.kernel.org,
Daniel Baluta <daniel.baluta@nxp.com>,
Peng Fan <peng.fan@nxp.com>, Frank Li <Frank.Li@nxp.com>
Subject: [PATCH v5 1/5] arm64: dts: imx8mp: Use resets property
Date: Mon, 17 Mar 2025 15:33:02 +0200 [thread overview]
Message-ID: <20250317133306.2003909-2-daniel.baluta@nxp.com> (raw)
In-Reply-To: <20250317133306.2003909-1-daniel.baluta@nxp.com>
Add resets property to dsp node in order to be able to control the dsp
run/stall bit from audio block control.
Reviewed-by: Peng Fan <peng.fan@nxp.com>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
---
arch/arm64/boot/dts/freescale/imx8mp.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
index ce6793b2d57e..3b725fe442d0 100644
--- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
@@ -6,6 +6,7 @@
#include <dt-bindings/clock/imx8mp-clock.h>
#include <dt-bindings/power/imx8mp-power.h>
#include <dt-bindings/reset/imx8mp-reset.h>
+#include <dt-bindings/reset/imx8mp-reset-audiomix.h>
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/input/input.h>
#include <dt-bindings/interconnect/fsl,imx8mp.h>
@@ -2422,6 +2423,8 @@ dsp: dsp@3b6e8000 {
mboxes = <&mu2 2 0>, <&mu2 2 1>,
<&mu2 3 0>, <&mu2 3 1>;
memory-region = <&dsp_reserved>;
+ resets = <&audio_blk_ctrl IMX8MP_AUDIOMIX_DSP_RUNSTALL>;
+ reset-names = "runstall";
status = "disabled";
};
};
--
2.43.0
next prev parent reply other threads:[~2025-03-17 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 13:33 [PATCH v5 0/5] Configure imx8mp dsp node for rproc usage Daniel Baluta
2025-03-17 13:33 ` Daniel Baluta [this message]
2025-03-17 13:33 ` [PATCH v5 2/5] arm64: dts: imx8mp: Add mu2 root clock Daniel Baluta
2025-03-17 15:30 ` Alexander Stein
2025-03-17 15:58 ` Daniel Baluta
2025-03-17 13:33 ` [PATCH v5 3/5] arm64: dts: imx8mp: Configure dsp node for rproc usage Daniel Baluta
2025-03-17 13:33 ` [PATCH v5 4/5] arm64: dts: imx8mp: Add DSP clocks Daniel Baluta
2025-03-17 13:33 ` [PATCH v5 5/5] arm64: dts: Add dsp rproc related mem regions Daniel Baluta
2025-03-17 20:37 ` [PATCH v5 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=20250317133306.2003909-2-daniel.baluta@nxp.com \
--to=daniel.baluta@nxp.com \
--cc=a.fatoum@pengutronix.de \
--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=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=peng.fan@nxp.com \
--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