All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] kselftest: alsa: Add simplistic test for ALSA mixer controls kselftest
Date: Mon, 6 Dec 2021 11:01:25 -0600	[thread overview]
Message-ID: <b2972e61-e6c2-9f60-6242-3762c88efe0a@linux.intel.com> (raw)
In-Reply-To: <Ya48u+Wx+ZZyfYIO@sirena.org.uk>


>>> +// This test will iterate over all cards detected in the system, exercising
> 
>> would it make sense to test only specific cards? People doing automated
>> tests might have a USB device for capture of analog loopbacks, or
>> injection of specific streams for capture, and usually care about
>> testing such devices - which do need manual setups and wiring btw.
> 
> It's not really idiomatic for kselftest to require any per system
> configuration by default - half the thing is that you can just run it
> and it should do as much as it can sensibly on the system.  You could
> definitely add some command line options for development or manual usage
> though.

I was thinking of adding this test to our CI, it's a bit orthogonal to
self-tests indeed. IIRC we check that we can modify all the PGA settings
for volume control but this test is a lot more generic.

  reply	other threads:[~2021-12-06 17:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 16:03 [PATCH v2] kselftest: alsa: Add simplistic test for ALSA mixer controls kselftest Mark Brown
2021-12-06 16:03 ` Mark Brown
2021-12-06 16:27 ` Pierre-Louis Bossart
2021-12-06 16:31   ` Pierre-Louis Bossart
2021-12-06 16:39   ` Mark Brown
2021-12-06 16:39     ` Mark Brown
2021-12-06 17:01     ` Pierre-Louis Bossart [this message]
2021-12-06 18:17       ` Mark Brown
2021-12-07  3:20 ` Takashi Sakamoto
2021-12-07  3:20   ` Takashi Sakamoto
2021-12-07  8:05   ` Jaroslav Kysela
2021-12-07 14:25   ` Mark Brown
2021-12-07 14:36     ` Takashi Iwai
2021-12-07 14:36       ` Takashi Iwai
2021-12-07 14:49       ` Mark Brown
2021-12-07 14:49         ` Mark Brown
2021-12-08 14:26     ` Takashi Sakamoto
2021-12-08 14:31       ` Takashi Sakamoto
2021-12-08 16:07       ` Mark Brown
2021-12-08 16:07         ` Mark Brown
2021-12-08 17:42 ` Shuah Khan
2021-12-08 17:42   ` Shuah Khan
2021-12-08 18:39   ` Mark Brown
2021-12-08 18:39     ` Mark Brown
2021-12-08 18:59     ` Shuah Khan
2021-12-08 18:59       ` Shuah Khan
2021-12-08 20:12       ` Mark Brown
2021-12-08 20:12         ` Mark Brown
2021-12-08 21:14         ` Shuah Khan
2021-12-08 21:14           ` Shuah Khan

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=b2972e61-e6c2-9f60-6242-3762c88efe0a@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.