Clarify DAPM does not expose any API to user space, and adapt the paragraph accordingly. Reviewed-by: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx> Reviewed-by: Bagas Sanjaya <bagasdotme@xxxxxxxxx> Signed-off-by: Luca Ceresoli <luca.ceresoli@xxxxxxxxxxx> --- 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
