From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-sound@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: [PATCH v2 05/12] ASoC: doc: dapm: clarify it's an internal API
Date: Fri, 26 Apr 2024 18:56:38 +0200 [thread overview]
Message-ID: <20240426-dapm-docs-v2-5-87b07547eb5b@bootlin.com> (raw)
In-Reply-To: <20240426-dapm-docs-v2-0-87b07547eb5b@bootlin.com>
Clarify DAPM does not expose any API to user space, and adapt the paragraph
accordingly.
Reviewed-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
---
Documentation/sound/soc/dapm.rst | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/sound/soc/dapm.rst b/Documentation/sound/soc/dapm.rst
index be849879274d..f96a32f137aa 100644
--- a/Documentation/sound/soc/dapm.rst
+++ b/Documentation/sound/soc/dapm.rst
@@ -11,9 +11,10 @@ subsystem at all times. It is independent of other kernel power
management frameworks and, as such, can easily co-exist with them.
DAPM is also completely transparent to all user space applications as
-all power switching is done within the ASoC core. No code changes or
-recompiling are required for user space applications. DAPM makes power
-switching decisions based upon any audio stream (capture/playback)
+all power switching is done internally to the ASoC core. For this reason
+DAPM does not expose a kernel API to user space and no code changes or
+recompiling are required for user space applications to use it. DAPM makes
+power switching decisions based upon any audio stream (capture/playback)
activity and audio mixer settings within the device.
DAPM spans the whole machine. It covers power control within the entire
--
2.34.1
next prev parent reply other threads:[~2024-04-26 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 16:56 [PATCH v2 00/12] ASoC: doc: dapm: various improvements Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 01/12] ASoC: doc: dapm: fix typos Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 02/12] ASoC: doc: dapm: fix struct name Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 03/12] ASoC: doc: dapm: minor rewording Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 04/12] ASoC: doc: dapm: remove dash after colon Luca Ceresoli
2024-04-26 16:56 ` Luca Ceresoli [this message]
2024-04-29 14:42 ` [PATCH v2 05/12] ASoC: doc: dapm: clarify it's an internal API Mark Brown
2024-04-26 16:56 ` [PATCH v2 06/12] ASoC: doc: dapm: replace "map" with "graph" Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 07/12] ASoC: doc: dapm: extend initial descrption Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 08/12] ASoC: doc: dapm: describe how widgets and routes are registered Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 09/12] ASoC: doc: dapm: fix and improve section "Registering DAPM controls" Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 10/12] ASoC: doc: dapm: improve section "Codec/DSP Widget Interconnections" Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 11/12] ASoC: doc: dapm: update section "DAPM Widget Events" Luca Ceresoli
2024-04-26 16:56 ` [PATCH v2 12/12] ASoC: doc: dapm: update event types Luca Ceresoli
2024-05-01 13:43 ` (subset) [PATCH v2 00/12] ASoC: doc: dapm: various improvements 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=20240426-dapm-docs-v2-5-87b07547eb5b@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bagasdotme@gmail.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=thomas.petazzoni@bootlin.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).