From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Daniel Baluta <daniel.baluta@nxp.com>,
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
Subject: Re: [PATCH v2 6/6] arm64: dts: Add dsp rproc related mem regions
Date: Tue, 26 Nov 2024 07:49:04 +0100 [thread overview]
Message-ID: <f8d5e367-5648-4941-9d65-adfbe6d3c0dc@pengutronix.de> (raw)
In-Reply-To: <20241125152427.136883-7-daniel.baluta@nxp.com>
On 25.11.24 16:24, Daniel Baluta wrote:
> 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>
Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-evk.dts b/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> index d26930f1a9e9..c732ee79772d 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> @@ -291,6 +291,16 @@ &aud2htx {
> status = "okay";
> };
>
> +&dsp_reserved {
> + status = "okay";
> +};
> +
> +&dsp {
> + memory-region = <&dsp_vdev0buffer>, <&dsp_vdev0vring0>,
> + <&dsp_vdev0vring1>, <&dsp_reserved>;
> + status = "okay";
> +};
> +
> &eqos {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_eqos>;
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-11-26 6:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 15:24 [PATCH v2 0/6] Configure imx8mp dsp node for rproc usage Daniel Baluta
2024-11-25 15:24 ` [PATCH v2 1/6] arm64: dts: imx8mp: Add mu2 root clock Daniel Baluta
2024-11-25 15:24 ` [PATCH v2 2/6] arm64: dts: imx8mp: Configure dsp node for rproc usage Daniel Baluta
2024-11-25 15:24 ` [PATCH v2 3/6] arm64: dts: imx8mp: Add DSP clocks Daniel Baluta
2024-11-25 15:24 ` [PATCH v2 4/6] dt-bindings: clock: imx8mp: Add syscon compatible Daniel Baluta
2024-11-25 16:25 ` Rob Herring (Arm)
2024-11-25 17:08 ` Frank Li
2024-11-26 15:31 ` Daniel Baluta
2024-11-26 16:36 ` Frank Li
2024-11-25 15:24 ` [PATCH v2 5/6] arm64: dts: imx8mp: Add fsl,dsp-ctrl property for dsp Daniel Baluta
2024-11-25 15:24 ` [PATCH v2 6/6] arm64: dts: Add dsp rproc related mem regions Daniel Baluta
2024-11-26 6:49 ` Ahmad Fatoum [this message]
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=f8d5e367-5648-4941-9d65-adfbe6d3c0dc@pengutronix.de \
--to=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=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®