From: Philipp Zabel <p.zabel@pengutronix.de>
To: 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 2/8] dt-bindings: dsp: fsl,dsp: Add resets property
Date: Thu, 20 Feb 2025 16:45:42 +0100 [thread overview]
Message-ID: <f69d6076f5b41bcf56ddbf24a72a600fa51466dc.camel@pengutronix.de> (raw)
In-Reply-To: <20250219192102.423850-3-daniel.baluta@nxp.com>
On Mi, 2025-02-19 at 21:20 +0200, Daniel Baluta wrote:
> On i.MX8MP we introduced support for using a reset controller
> to control DSP operation.
>
> This patch adds reset property which is required for i.MX8MP.
>
> Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
> ---
> .../devicetree/bindings/dsp/fsl,dsp.yaml | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/dsp/fsl,dsp.yaml b/Documentation/devicetree/bindings/dsp/fsl,dsp.yaml
> index ab93ffd3d2e5..923e7f079f1b 100644
> --- a/Documentation/devicetree/bindings/dsp/fsl,dsp.yaml
> +++ b/Documentation/devicetree/bindings/dsp/fsl,dsp.yaml
> @@ -82,6 +82,13 @@ properties:
> description:
> Phandle to syscon block which provide access for processor enablement
>
> + resets:
> + description:
> + A pair consisting of phandle to audio-blk-control and an index referencing
> + the DSP Run/Stall bit in audiomix registers.
> + See include/dt-bindings/reset/imx8mp-reset-audiomix.h for each index meaning.
> + maxItems: 1
This is going to be confusing when there is an actual (undocumented?)
DSP core reset that is not described in the device tree bindings, see
patch 8.
To me this looks like a bit of a gray zone, as I don't know how the
hardware actually works, but if you wouldn't call the Run/Stall bit a
reset, it probably shouldn't be described as such in the device tree
bindings.
I'm not sure. Should both core and runstall reset be described in the
device tree? Or only the core reset, or neither? Either way we should
try not to lie about the hardware here.
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 [this message]
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
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=f69d6076f5b41bcf56ddbf24a72a600fa51466dc.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=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).