On Thu, 2013-01-31 at 18:28 +0100, Clemens Ladisch wrote:
Brent Weatherall wrote:
At a high level, when configuring the built in audio device (3.5 mm jack), the device accepts ANY rate requested (via snd_pcm_set_rate_near). it accepts unsupported rates without alteration. If the rate is actually not supported, then 'snd_pcm_hw_params' fails with error '-22'.
This sounds as if the driver published incorrect constraints.
Do you have a pointer to the driver's source code?
The OMAP4 ABE driver doesn't actually know the exact constraints if there is not a valid playback path between source PCM and sink (it will still throw out anything insane though). This is because it can route audio from most of it's PCMs to most of it's components, e.g. HS, HF, BT, MODEM, Earpiece, etc where some components have different constraints. It's possible that you dont have a path in your case.
Can you check you have enabled a valid playback path with alsaucm/alsamixer and then test with aplay. This should help narrow down the issue.
I've CC'ed Peter since 3.4 is a little old and he is working on the latest OMAP4 codebase.
Regards
Liam