From: Takashi Iwai <tiwai@suse.de>
To: Yu-Hsuan Hsu <yuhsuan@chromium.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Alsa conformance test - a new test for ALSA drivers
Date: Thu, 05 Sep 2019 17:17:09 +0200 [thread overview]
Message-ID: <s5h5zm6pybu.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAGvk5Pohb9cxL=Mu11RPVD66NdiZkG+vO9TEtqBWe1tnBn6qyQ@mail.gmail.com>
On Wed, 04 Sep 2019 06:29:30 +0200,
Yu-Hsuan Hsu wrote:
>
> Hi all,
>
> I have created an new tool "Alsa conformance test"(
> https://chromium.googlesource.com/chromiumos/platform/audiotest/+/master/alsa_conformance_test.md),
> which is used for verifying ALSA drivers. Here are some main functions it
> can measure:
> 1. Correctness of hw_params
> 2. Stability of rate
> 3. Stability of step
> 4. Runtime of each ALSA API
> 5. Underrun and Overrun
>
> I recommend to use the script "alsa_conformance_test.py" inside. Just give
> it a device and then it will test the below functions automatically.
> 1. To make sure whether all the parameters provided by an ALSA driver can
> be used.
> 2. To make sure whether the measured rate is the same as the expected rate.
>
> We have used this tool to find out many issues in ChromeOS. I hope it can
> help development in Linux too. If you have any problems or want more
> features, please create a bug in crbug.com and assign to me (
> yuhsuan@chromium.org). Thanks!
Great, it's something I wanted to see for long time.
Let us know if you'd like to put this to ALSA upstream.
thanks,
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-09-05 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 4:29 [alsa-devel] Alsa conformance test - a new test for ALSA drivers Yu-Hsuan Hsu
2019-09-05 15:17 ` Takashi Iwai [this message]
2019-09-06 8:06 ` Yu-Hsuan Hsu
2019-09-09 12:06 ` 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=s5h5zm6pybu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=yuhsuan@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).