From: Myroslav Demchenko <myro@myromyro.com>
To: perex@perex.cz, tiwai@suse.com
Cc: corbet@lwn.net, skhan@linuxfoundation.org,
linux-sound@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, mirademche@gmail.com,
Myroslav Demchenko <myro@myromyro.com>
Subject: [PATCH] docs: sound: clarify PulseAudio and PipeWire configuration description
Date: Fri, 13 Mar 2026 13:01:40 +0100 [thread overview]
Message-ID: <20260313120140.45022-1-myro@myromyro.com> (raw)
Modern sound servers such as PulseAudio and PipeWire support dynamic
configuration, so this feature is rarely needed today. However, it
was useful in the past when audio setups relied on static configuration.
Signed-off-by: Myroslav Demchenko <myro@myromyro.com>
---
Documentation/sound/alsa-configuration.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/sound/alsa-configuration.rst b/Documentation/sound/alsa-configuration.rst
index 55b845d38236..a3d8da5a3f6c 100644
--- a/Documentation/sound/alsa-configuration.rst
+++ b/Documentation/sound/alsa-configuration.rst
@@ -142,9 +142,9 @@ in primary usage, and people would like to assign it as the first
appearing card. They can do it by specifying "index=1,0" module
parameter, which will swap the assignment slots.
-Today, with the sound backend like PulseAudio and PipeWire which
-supports dynamic configuration, it's of little use, but that was a
-help for static configuration in the past.
+Today, sound servers such as PulseAudio and PipeWire support dynamic
+configuration, so this feature is rarely needed. However, it was
+useful in the past when audio setups relied on static configuration.
Module snd-adlib
----------------
--
2.53.0
next reply other threads:[~2026-03-13 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 12:01 Myroslav Demchenko [this message]
2026-03-14 13:34 ` [PATCH] docs: sound: clarify PulseAudio and PipeWire configuration description Takashi Iwai
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=20260313120140.45022-1-myro@myromyro.com \
--to=myro@myromyro.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mirademche@gmail.com \
--cc=perex@perex.cz \
--cc=skhan@linuxfoundation.org \
--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