From: Philipp Zabel <p.zabel@pengutronix.de>
To: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
robh@kernel.org, shawnguo@kernel.org
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
mathieu.poirier@linaro.org, shengjiu.wang@nxp.com,
Frank.Li@nxp.com, peng.fan@nxp.com, laurentiu.mihalcea@nxp.com,
iuliana.prodan@nxp.com
Subject: Re: [PATCH v2 8/8] imx_dsp_rproc: Use reset controller API to control the DSP
Date: Thu, 20 Feb 2025 16:45:39 +0100 [thread overview]
Message-ID: <6e03b0c09c4e6d222670025c6540f73a0a0a819d.camel@pengutronix.de> (raw)
In-Reply-To: <c52e6c5c-f49e-4727-b669-086ae7cb0e1e@gmail.com>
On Do, 2025-02-20 at 00:22 +0200, Laurentiu Mihalcea wrote:
>
> On 2/19/2025 9:21 PM, Daniel Baluta wrote:
> > Use the reset controller API to control the DSP on i.MX8MP. This way
> > we can have a better control of the resources and avoid using a syscon
> > to access the audiomix bits.
> >
> > Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
> > Reviewed-by: Peng Fan <peng.fan@nxp.com>
> > ---
> > drivers/remoteproc/imx_dsp_rproc.c | 25 +++++++++++++++++--------
> > drivers/remoteproc/imx_rproc.h | 2 ++
> > 2 files changed, 19 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/remoteproc/imx_dsp_rproc.c b/drivers/remoteproc/imx_dsp_rproc.c
> > index ea5024919c2f..631563e4f86d 100644
> > --- a/drivers/remoteproc/imx_dsp_rproc.c
> > +++ b/drivers/remoteproc/imx_dsp_rproc.c
> > @@ -19,6 +19,7 @@
> > #include <linux/pm_runtime.h>
> > #include <linux/regmap.h>
> > #include <linux/remoteproc.h>
> > +#include <linux/reset.h>
> > #include <linux/slab.h>
> >
> > #include "imx_rproc.h"
> > @@ -111,6 +112,7 @@ enum imx_dsp_rp_mbox_messages {
> > */
> > struct imx_dsp_rproc {
> > struct regmap *regmap;
> > + struct reset_control *reset;
>
> Maybe rename this to "stall"? There's also the DAP stuff that's actually used
> to reset the core so this might be a bit confusing?
So Run/Stall does not actually reset anything? Maybe then it should not
be modeled as a reset control. It looks to me like the
DAP_PWRCTL[CORERESET] bit in the Audio Processor Debug region would be
a much better fit.
regards
Philipp
next prev parent reply other threads:[~2025-02-20 15:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 19:20 [PATCH v2 0/8] imx8mp: Add support to Run/Stall DSP via reset API Daniel Baluta
2025-02-19 19:20 ` [PATCH v2 1/8] dt-bindings: reset: audiomix: Add reset ids for EARC and DSP Daniel Baluta
2025-02-19 21:19 ` Frank Li
2025-02-21 22:27 ` Rob Herring (Arm)
2025-02-19 19:20 ` [PATCH v2 2/8] dt-bindings: dsp: fsl,dsp: Add resets property Daniel Baluta
2025-02-19 21:18 ` Rob Herring (Arm)
2025-02-19 21:26 ` Frank Li
2025-02-20 10:36 ` Alexander Stein
2025-02-20 13:11 ` Daniel Baluta
2025-02-20 14:56 ` Alexander Stein
2025-02-20 15:45 ` Philipp Zabel
2025-02-20 17:17 ` Frank Li
2025-02-19 19:20 ` [PATCH v2 3/8] arm64: dts: imx8mp: Add resets to dsp node Daniel Baluta
2025-02-19 21:28 ` Frank Li
2025-02-19 19:20 ` [PATCH v2 4/8] reset: imx8mp-audiomix: Add prefix for internal macro Daniel Baluta
2025-02-19 19:20 ` [PATCH v2 5/8] reset: imx8mp-audiomix: Prepare the code for more reset bits Daniel Baluta
2025-02-19 21:31 ` Frank Li
2025-02-19 19:21 ` [PATCH v2 6/8] reset: imx8mp-audiomix: Introduce active_low configuration option Daniel Baluta
2025-02-19 19:21 ` [PATCH v2 7/8] reset: imx8mp-audiomix: Add support for DSP run/stall Daniel Baluta
2025-02-19 21:31 ` Frank Li
2025-02-19 19:21 ` [PATCH v2 8/8] imx_dsp_rproc: Use reset controller API to control the DSP Daniel Baluta
2025-02-19 21:33 ` Frank Li
2025-02-19 22:22 ` Laurentiu Mihalcea
2025-02-20 15:45 ` Philipp Zabel [this message]
2025-02-21 1:20 ` Laurentiu Mihalcea
2025-02-21 8:52 ` 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=6e03b0c09c4e6d222670025c6540f73a0a0a819d.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.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=laurentiumihalcea111@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).