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.
Anyway, in summary, the tests I'm thinking of are:
- Ramp test: the gold standard for driver/SoC testing.
- Impulse response test: the gold standard for phase/alignment issues.
- Time domain testy thingy: a less good ramp test if you can't manage digital loopback in your system.
This sounds great. Lets get the first part upstream and then we can incrementally add the other tests. Btw, are you going to the audio mini conf at ELCE in Dublin ? It would be good to discuss this in person !
No, not planning to go to Dublin, though it's not a bad idea. I'm not sure I can justify the trip there (I'm in California). My day job is to be a DSP/Acoustical/Electrical engineer, and I'm only hacking on the kernel because we need to get it working :-). Which I guess is also my day job now too. Make that DSP/Acoustical/Electrical/Hack engineer.
We can always chat via Skype or phone, though I agree, there's nothing like talking face to face.
Liam
-Caleb