From: Jaroslav Kysela <perex@perex.cz>
To: Ivan Orlov <ivan.orlov0322@gmail.com>,
tiwai@suse.com, corbet@lwn.net, broonie@kernel.org,
skhan@linuxfoundation.org
Cc: alsa-devel@alsa-project.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
gregkh@linuxfoundation.org, himadrispandya@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v3 2/3] ALSA: Implement the new Virtual PCM Test Driver
Date: Tue, 6 Jun 2023 15:50:58 +0200 [thread overview]
Message-ID: <afd4bdef-7511-66dd-e021-6eaafabdbba2@perex.cz> (raw)
In-Reply-To: <20230606133807.14089-2-ivan.orlov0322@gmail.com>
On 06. 06. 23 15:38, Ivan Orlov wrote:
> We have a lot of different virtual media drivers, which can be used for
> testing of the userspace applications and media subsystem middle layer.
> However, all of them are aimed at testing the video functionality and
> simulating the video devices. For audio devices we have only snd-dummy
> module, which is good in simulating the correct behavior of an ALSA device.
> I decided to write a tool, which would help to test the userspace ALSA
> programs (and the PCM middle layer as well) under unusual circumstances
> to figure out how they would behave. So I came up with this Virtual PCM
> Test Driver.
Acked-by: Jaroslav Kysela <perex@perex.cz>
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2023-06-06 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 13:38 [PATCH v3 1/3] docs: sound: add 'pcmtest' driver documentation Ivan Orlov
2023-06-06 13:38 ` [PATCH v3 2/3] ALSA: Implement the new Virtual PCM Test Driver Ivan Orlov
2023-06-06 13:50 ` Jaroslav Kysela [this message]
2023-06-06 13:38 ` [PATCH v3 3/3] selftests: ALSA: Add test for the 'pcmtest' driver Ivan Orlov
2023-06-06 13:51 ` Jaroslav Kysela
2023-06-06 13:50 ` [PATCH v3 1/3] docs: sound: add 'pcmtest' driver documentation Jaroslav Kysela
2023-06-08 5:14 ` Bagas Sanjaya
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=afd4bdef-7511-66dd-e021-6eaafabdbba2@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=himadrispandya@gmail.com \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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