From: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
To: Daniel Baluta <daniel.baluta@nxp.com>,
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
Subject: Re: [PATCH v7 0/5] Configure imx8mp dsp node for rproc usage
Date: Thu, 10 Apr 2025 15:23:45 +0300 [thread overview]
Message-ID: <fb40d405-9f76-4117-88f9-423ea5fac3f0@gmail.com> (raw)
In-Reply-To: <20250320121004.2542314-1-daniel.baluta@nxp.com>
On 3/20/2025 2:09 PM, Daniel Baluta wrote:
> DSP found in i.MX8MP SOC can be used by multiple frameworks in order to
> enable various applications:
> - rproc/rpmsg framework, used to load for example Zephyr samples
> - Sound Open Firmware, used to enable various audio processing
> pipelines.
>
> Current dsp node was configured with SOF in mind but it doesn't work
> well with imx8mp-evk dts. SOF controls audio IPs from firmware side
> while imx8mp-evk.dts preffers to control audio IPs from Linux side.
>
> So, configure 'dsp' node to be used with rproc scenario and later will
> add a separate dts or an overlay to configure the node for SOF.
>
> This patch series configures and enables dsp node to be used with rproc.
>
> Changes since v6:
> - addressed Alexander Stein comments
> - enable mu2 separately in patch 5/5
> - put "status" always as the last in node definition
>
> Changes since v5:
> - do not enable mu2 node by default
> - fix dt_bindings errors
>
> Changes since v4:
> (https://lore.kernel.org/linux-arm-kernel/Z6zGLn3B6SVXhTV1@lizhi-Precision-Tower-5810/T/)·······························································································
> - after comments received on v4, we implemented the run/stall
> bits using reset controller API (changes merged ->
> https://patchwork.kernel.org/project/linux-arm-kernel/cover/20250311085812.1296243-1-daniel.baluta@nxp.com/)
> - drop patches related to DSP run/stall/reset via syscon
> - picked up patch related to using run_stall via reset
> controller API.
>
>
> Daniel Baluta (5):
> arm64: dts: imx8mp: Use resets property
> arm64: dts: imx8mp: Add mu2 root clock
> arm64: dts: imx8mp: Configure dsp node for rproc usage
> arm64: dts: imx8mp: Add DSP clocks
> arm64: dts: Enable DSP node for remoteproc usage
>
> arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 14 +++++++++++++
> arch/arm64/boot/dts/freescale/imx8mp.dtsi | 22 +++++++++++++-------
> 2 files changed, 29 insertions(+), 7 deletions(-)
>
For the whole series:
Reviewed-by: Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>
next prev parent reply other threads:[~2025-04-10 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 12:09 [PATCH v7 0/5] Configure imx8mp dsp node for rproc usage Daniel Baluta
2025-03-20 12:09 ` [PATCH v7 1/5] arm64: dts: imx8mp: Use resets property Daniel Baluta
2025-03-20 12:09 ` [PATCH v7 2/5] arm64: dts: imx8mp: Add mu2 root clock Daniel Baluta
2025-03-20 12:09 ` [PATCH v7 3/5] arm64: dts: imx8mp: Configure dsp node for rproc usage Daniel Baluta
2025-03-20 12:09 ` [PATCH v7 4/5] arm64: dts: imx8mp: Add DSP clocks Daniel Baluta
2025-03-20 12:09 ` [PATCH v7 5/5] arm64: dts: Enable DSP node for remoteproc usage Daniel Baluta
2025-04-10 12:23 ` Laurentiu Mihalcea [this message]
2025-04-15 7:40 ` [PATCH v7 0/5] Configure imx8mp dsp node for rproc usage Daniel Baluta
2025-04-22 3:07 ` Shawn Guo
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=fb40d405-9f76-4117-88f9-423ea5fac3f0@gmail.com \
--to=laurentiumihalcea111@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.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=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