From: Chancel Liu <chancel.liu@nxp.com>
To: lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
shengjiu.wang@gmail.com, Xiubo.Lee@gmail.com, festevam@gmail.com,
nicoleotsuka@gmail.com, perex@perex.cz, tiwai@suse.com,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Chancel Liu <chancel.liu@nxp.com>
Subject: [PATCH v2 1/2] ASoC: dt-bindings: fsl_rpmsg: List DAPM endpoints ignoring system suspend
Date: Mon, 25 Sep 2023 19:09:45 +0800 [thread overview]
Message-ID: <20230925110946.3156100-1-chancel.liu@nxp.com> (raw)
Add a property to list DAPM endpoints which mark paths between these
endpoints should not be disabled when system enters in suspend state.
LPA means low power audio case. On asymmetric multiprocessor, there are
Cortex-A core and Cortex-M core, Linux is running on Cortex-A core,
RTOS or other OS is running on Cortex-M core. The audio hardware
devices can be controlled by Cortex-M. LPA can be explained as a
mechanism that Cortex-A allocates a large buffer and fill audio data,
then Cortex-A can enter into suspend for the purpose of power saving.
Cortex-M continues to play the sound during suspend phase of Cortex-A.
When the data in buffer is consumed, Cortex-M will trigger the Cortex-A
to wakeup to fill data. LPA requires some audio paths still enabled
when Cortex-A enters into suspend.
Signed-off-by: Chancel Liu <chancel.liu@nxp.com>
---
.../devicetree/bindings/sound/fsl,rpmsg.yaml | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml b/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml
index 188f38baddec..d8fd17615bf2 100644
--- a/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml
+++ b/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml
@@ -91,6 +91,21 @@ properties:
- rpmsg-audio-channel
- rpmsg-micfil-channel
+ fsl,lpa-widgets:
+ $ref: /schemas/types.yaml#/definitions/non-unique-string-array
+ description: |
+ A list of DAPM endpoints which mark paths between these endpoints should
+ not be disabled when system enters in suspend state. LPA means low power
+ audio case. On asymmetric multiprocessor, there are Cortex-A core and
+ Cortex-M core, Linux is running on Cortex-A core, RTOS or other OS is
+ running on Cortex-M core. The audio hardware devices can be controlled by
+ Cortex-M. LPA can be explained as a mechanism that Cortex-A allocates a
+ large buffer and fill audio data, then Cortex-A can enter into suspend
+ for the purpose of power saving. Cortex-M continues to play the sound
+ during suspend phase of Cortex-A. When the data in buffer is consumed,
+ Cortex-M will trigger the Cortex-A to wakeup to fill data. LPA requires
+ some audio paths still enabled when Cortex-A enters into suspend.
+
required:
- compatible
--
2.25.1
next reply other threads:[~2023-09-25 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 11:09 Chancel Liu [this message]
2023-09-25 11:09 ` [PATCH v2 2/2] ASoC: imx-rpmsg: Force codec power on in low power audio mode Chancel Liu
2023-09-25 12:25 ` [PATCH v2 1/2] ASoC: dt-bindings: fsl_rpmsg: List DAPM endpoints ignoring system suspend Mark Brown
2023-09-27 3:07 ` Chancel Liu
2023-09-27 9:29 ` Mark Brown
2023-10-07 11:13 ` [EXT] " Chancel Liu
2023-10-09 16:36 ` Mark Brown
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=20230925110946.3156100-1-chancel.liu@nxp.com \
--to=chancel.liu@nxp.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@gmail.com \
--cc=tiwai@suse.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).