From: HyeongJun An <sammiee5311@gmail.com>
To: tiwai@suse.com
Cc: perex@perex.cz, ivan.orlov0322@gmail.com, broonie@kernel.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
HyeongJun An <sammiee5311@gmail.com>
Subject: [PATCH v2 0/2] ALSA: pcmtest: Add a volume control with event fault injection
Date: Wed, 11 Nov 2026 18:04:27 +0900 [thread overview]
Message-ID: <cover.1794386073.git.sammiee5311@gmail.com> (raw)
Hello Takashi,
This is the non-RFC version of [1], which Mark found reasonable [2].
Patch 1 fixes the places where pcmtest.rst does not match the driver.
Patch 2 adds the volume control and its two fault parameters, and
documents them.
mixer-test results on the new control, under qemu on sound/for-next:
no fault all 8 checks pass
inject_ctl_no_event=1 only event_missing fails
inject_ctl_spurious_event=1 only event_spurious fails
The pcmtest selftest still passes all 10 tests.
Changes since the RFC:
- document the new parameters
- rename the control to "Test Playback Volume", which the OSS mixer
emulation does not map
- add the documentation fix as patch 1
[1] https://lore.kernel.org/all/20261103011000.1012035-1-sammiee5311@gmail.com/
[2] https://lore.kernel.org/all/61df01a7-10ee-407e-879f-d9c1085a5d43@sirena.org.uk/
Prepared with Claude Code (Claude Opus 5.5). Tested on x86_64 under qemu.
Best regards,
HyeongJun An
HyeongJun An (2):
ALSA: doc: pcmtest: Update to match the driver
ALSA: pcmtest: Add a volume control with event fault injection
Documentation/sound/cards/pcmtest.rst | 25 ++++++++--
sound/drivers/pcmtest.c | 68 +++++++++++++++++++++++++++
2 files changed, 89 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-11 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 9:04 HyeongJun An [this message]
2026-11-11 9:04 ` [PATCH v2 1/2] ALSA: doc: pcmtest: Update to match the driver HyeongJun An
2026-11-11 9:04 ` [PATCH v2 2/2] ALSA: pcmtest: Add a volume control with event fault injection HyeongJun An
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=cover.1794386073.git.sammiee5311@gmail.com \
--to=sammiee5311@gmail.com \
--cc=broonie@kernel.org \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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
all inboxes | Powered by JetHome®