alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Caleb Crome <caleb@crome.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	han.lu@intel.com,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@kernel.org>,
	bernard.gautier@intel.com
Subject: Re: [PATCH BAT V1 0/7] BAT: Add Basic Audio Tester command line tool
Date: Fri, 18 Sep 2015 10:09:07 +0100	[thread overview]
Message-ID: <1442567347.7634.12.camel@loki> (raw)
In-Reply-To: <CAG5mAdw1jjVGeTi2k0QLCTVv+Qr-Hy3UMZLuT1M=f2uHje32kw@mail.gmail.com>

On Thu, 2015-09-17 at 06:29 -0700, Caleb Crome wrote:
> >> > We have also used BAT for stress testing audio over D0 -> D3 -> D0 transitions.
> >>
> >> Sorry, I'm not familiar with that terminology.  Are those the
> >> different power states?
> >
> > Yes, PM suspend and resume of device. We have some scripts (to be
> > upstreamed later) that would play audio, suspend the device, resume the
> > device and then retest the audio.
> 
> That seems particularly likely to result in multiple codecs getting
> out of phase alignment.  i.e. when restarting, you want to be sure to
> follow the same startup procedure as the first time to make sure all
> codecs are aligned.
> 

This was more for testing our DSP and codec context was properly
saved/restored and also our codec was properly powered down/up during PM
state changes.

Liam

  parent reply	other threads:[~2015-09-18  9:09 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 [this message]
2015-09-16 16:37 ` Mark Brown
2015-09-16 16:57   ` Liam Girdwood
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=1442567347.7634.12.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=caleb@crome.org \
    --cc=han.lu@intel.com \
    --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 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).