From mboxrd@z Thu Jan 1 00:00:00 1970 From: Liam Girdwood Subject: Re: [PATCH BAT V1 0/7] BAT: Add Basic Audio Tester command line tool Date: Fri, 18 Sep 2015 10:09:07 +0100 Message-ID: <1442567347.7634.12.camel@loki> References: <1442403626.10528.50.camel@loki> <1442486431.2520.34.camel@loki> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by alsa0.perex.cz (Postfix) with ESMTP id 388B32604D3 for ; Fri, 18 Sep 2015 11:09:14 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Caleb Crome Cc: Takashi Iwai , han.lu@intel.com, "alsa-devel@alsa-project.org" , Mark Brown , bernard.gautier@intel.com List-Id: alsa-devel@alsa-project.org 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