From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
Shuah Khan <shuah@kernel.org>,
alsa-devel@alsa-project.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/7] kselftest/alsa: pcm-test improvements
Date: Mon, 02 Jan 2023 18:09:55 +0100 [thread overview]
Message-ID: <87fscssw0s.wl-tiwai@suse.de> (raw)
In-Reply-To: <20221208-alsa-pcm-test-hacks-v4-0-5a152e65b1e1@kernel.org>
On Tue, 27 Dec 2022 18:06:46 +0100,
Mark Brown wrote:
>
> This series provides a bunch of quick updates which should make the
> coverage from pcm-test a bit more useful, it adds some support for
> skipping tests when the hardware/driver is unable to support the
> requested configuration, support for providing user visible descriptions
> and then expands the set of cases we cover to include more sample rates
> and channel counts. This should exercise switching between 8kHz and
> 44.1kHz based rates and ensure that clocking doesn't get confused by
> non-stereo channel counts, both of which are I expect common real world
> errors, at least for embedded cards.
>
> v4:
> - Rebase onto v6.2-rc1.
> v3:
> - "Rebase" onto Takashi's current tree (with a revert).
> - Include Jaroslav's changes to specify all tests in the configuration
> file parsing.
> - Add a new "description" field to the configuration instead of trying
> to name the tests.
> - Always run both default and per-system tests, logging our success at
> setting the per-system configurations as a separate test since they
> shouldn't fail.
> v2:
> - Rebase onto Takashi's current tree.
> - Tweak the buffer sizes for the newly added cases, don't be quite
> so ambitious in how big a buffer we request for 96kHz and don't
> go quite so small for 8kHz since some devices start hitting lower
> limits on period size and struggle to deliver accurate timing.
>
> To: Takashi Iwai <tiwai@suse.com>
> To: Jaroslav Kysela <perex@perex.cz>
> To: Shuah Khan <shuah@kernel.org>
> Cc: alsa-devel@alsa-project.org
> Cc: linux-kselftest@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Mark Brown <broonie@kernel.org>
Applied all patches now to for-next branch.
thanks,
Takashi
prev parent reply other threads:[~2023-01-02 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 17:06 [PATCH v4 0/7] kselftest/alsa: pcm-test improvements Mark Brown
2022-12-27 17:06 ` [PATCH v4 1/7] kselftest/alsa: pcm - Drop recent coverage improvement changes Mark Brown
2022-12-27 17:06 ` [PATCH v4 2/7] kselftest/alsa: pcm - move more configuration to configuration files Mark Brown
2022-12-27 17:06 ` [PATCH v4 3/7] kselftest/alsa: pcm - Always run the default set of tests Mark Brown
2022-12-27 17:06 ` [PATCH v4 4/7] kselftest/alsa: pcm - skip tests when we fail to set params Mark Brown
2022-12-27 17:06 ` [PATCH v4 5/7] kselftest/alsa: pcm - Support optional description for tests Mark Brown
2022-12-27 17:06 ` [PATCH v4 6/7] kselftest/alsa: pcm - Provide descriptions for the default tests Mark Brown
2022-12-27 17:06 ` [PATCH v4 7/7] kselftest/alsa: pcm - Add more coverage by default Mark Brown
2023-01-02 17:09 ` Takashi Iwai [this message]
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=87fscssw0s.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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