alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: han.lu@intel.com, alsa-devel@alsa-project.org, tiwai@suse.com,
	bernard.gautier@intel.com
Subject: Re: [PATCH BAT V1 0/7] BAT: Add Basic Audio Tester command line tool
Date: Wed, 16 Sep 2015 17:57:00 +0100	[thread overview]
Message-ID: <1442422620.10528.133.camel@loki> (raw)
In-Reply-To: <20150916163758.GJ12027@sirena.org.uk>

On Wed, 2015-09-16 at 17:37 +0100, Mark Brown wrote:
> On Tue, Sep 15, 2015 at 03:00:16PM +0800, han.lu@intel.com wrote:
> 
> > BAT works by playing an audio stream and capturing the same stream
> > in either a digital or analog loopback. It then compares the captured
> > stream to the original to determine if the testcase passes or fails.
> 
> This is really cool, sounds like there's some overlap with the tool
> David wrote to verify TLV information?  Actually in that vein one thing
> I started looking at but parked until this got posted is something that
> goes through and tries to stress test control value settings (trying to
> set out of bounds values, make sure all valid settings can be used and
> so on).  That's probably better kept as a separate tool I think given
> that it doesn't really overlap with audio streaming.

I didn't think of bounds testing the controls :) Especially useful for
DSPs where we could overflow or crash FW if certain combinations of
enumerated controls are used.

We were looking at testing the gains too, to make sure that a 6dB
control gain really does mean a 6dB gain in signal. It's in the TODO
list. Most of the code is already there to do this, but we were looking
to upstream first and then incrementally add features. I think Han plans
to upstream the tinyalsa support after the initial code is upstream
though.

Liam

  reply	other threads:[~2015-09-16 16:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  7:00 [PATCH BAT V1 0/7] BAT: Add Basic Audio Tester command line tool han.lu
2015-09-15  7:00 ` [PATCH BAT V1 1/7] BAT: Add initial functions han.lu
2015-09-15  7:00 ` [PATCH BAT V1 2/7] BAT: Add common definitions and functions han.lu
2015-09-15  7:00 ` [PATCH BAT V1 3/7] BAT: Add playback and record functions han.lu
2015-09-15  7:00 ` [PATCH BAT V1 4/7] BAT: Add signal generator han.lu
2015-09-18 16:50   ` Caleb Crome
2015-09-21  6:44     ` Liam Girdwood
2015-09-15  7:00 ` [PATCH BAT V1 5/7] BAT: Add converting functions han.lu
2015-09-15  7:00 ` [PATCH BAT V1 6/7] BAT: Add spectrum analysis functions han.lu
2015-09-15  7:00 ` [PATCH BAT V1 7/7] BAT: Add Makefile and configures han.lu
2015-09-16  3:23 ` [PATCH BAT V1 0/7] BAT: Add Basic Audio Tester command line tool Caleb Crome
2015-09-16 11:40   ` Liam Girdwood
2015-09-16 16:43     ` Caleb Crome
2015-09-17 10:40       ` Liam Girdwood
2015-09-17 13:29         ` Caleb Crome
2015-09-17 17:42           ` Mark Brown
2015-09-17 18:50             ` Caleb Crome
2015-09-17 22:40               ` Caleb Crome
2015-09-17 23:00                 ` James Cameron
2015-09-17 23:30                   ` Caleb Crome
2015-09-18  9:09           ` Liam Girdwood
2015-09-16 16:37 ` Mark Brown
2015-09-16 16:57   ` Liam Girdwood [this message]
2015-09-16 20:34     ` Mark Brown
2015-09-19 16:40 ` Takashi Iwai
2015-09-21  6:33   ` Liam Girdwood

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=1442422620.10528.133.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bernard.gautier@intel.com \
    --cc=broonie@kernel.org \
    --cc=han.lu@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).