From: HyeongJun An <sammiee5311@gmail.com>
To: Takashi Iwai <tiwai@suse.com>
Cc: Ivan Orlov <ivan.orlov0322@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Shuah Khan <shuah@kernel.org>,
linux-sound@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
HyeongJun An <sammiee5311@gmail.com>
Subject: [PATCH 0/3] selftests: ALSA: pcmtest: Test error injection and pause
Date: Thu, 22 Oct 2026 20:12:41 +0900 [thread overview]
Message-ID: <cover.1792660433.git.sammiee5311@gmail.com> (raw)
The pcmtest driver can return errors from its PCM callbacks and
supports pause, but the selftest covers neither. This series adds tests
for both.
Patch 1 moves the capture data check into a helper, so patch 3 can
reuse it. Patch 2 tests each inject_*_err parameter. Patch 3 tests
pausing a capture stream.
Tested on x86_64 with the sound/for-next driver, built for a 6.17 host.
All 10 tests pass in three runs. To check that the pause test catches
real bugs, I loaded two broken drivers. One keeps running on PAUSE_PUSH.
The other restarts the data on PAUSE_RELEASE. Only capture_pause fails
on each.
HyeongJun An (3):
selftests: ALSA: pcmtest: Move the capture data check into a helper
selftests: ALSA: pcmtest: Test errors from the PCM callbacks
selftests: ALSA: pcmtest: Test pausing a capture stream
.../selftests/alsa/test-pcmtest-driver.c | 167 +++++++++++++++++-
1 file changed, 158 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2026-10-22 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 11:12 HyeongJun An [this message]
2026-10-22 11:12 ` [PATCH 1/3] selftests: ALSA: pcmtest: Move the capture data check into a helper HyeongJun An
2026-10-22 11:12 ` [PATCH 2/3] selftests: ALSA: pcmtest: Test errors from the PCM callbacks HyeongJun An
2026-10-22 11:12 ` [PATCH 3/3] selftests: ALSA: pcmtest: Test pausing a capture stream HyeongJun An
2026-10-23 13:35 ` [PATCH 0/3] selftests: ALSA: pcmtest: Test error injection and pause 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=cover.1792660433.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-kselftest@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=shuah@kernel.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
all inboxes | Powered by JetHome®