[alsa-devel] Wrong sample rate user space -> kernel space?
On a PXA embedded board, the sample rate propagation from user space to kernel space seems to be wrong.
When I start aplay (v1.0.19) from userspace like this ...
# aplay -f dat /dev/urandom Playing raw data '/dev/urandom' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
... params_rate(params) in my snd_soc_ops .hw_params callback returns 88200, not 48000.
Can anyone reproduce this? I guess this is unrelated to PXA and ASoC.
Thanks, Daniel
Daniel Mack wrote:
On a PXA embedded board, the sample rate propagation from user space to kernel space seems to be wrong.
When I start aplay (v1.0.19) from userspace like this ...
# aplay -f dat /dev/urandom Playing raw data '/dev/urandom' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo... params_rate(params) in my snd_soc_ops .hw_params callback returns 88200, not 48000.
It might be possible that userspace converts the sample rate because it thinks that the driver doesn't support 48 kHz.
Is there a converter plugin in the output of "aplay -f dat -v /dev/urandom"?
Best regards, Clemens
On Tue, Jul 07, 2009 at 05:10:00PM +0200, Clemens Ladisch wrote:
Daniel Mack wrote:
On a PXA embedded board, the sample rate propagation from user space to kernel space seems to be wrong.
When I start aplay (v1.0.19) from userspace like this ...
# aplay -f dat /dev/urandom Playing raw data '/dev/urandom' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo... params_rate(params) in my snd_soc_ops .hw_params callback returns 88200, not 48000.
It might be possible that userspace converts the sample rate because it thinks that the driver doesn't support 48 kHz.
Is there a converter plugin in the output of "aplay -f dat -v /dev/urandom"?
Argh. Of course, you're right. Sorry for the noise. Literally ;)
Daniel
participants (2)
-
Clemens Ladisch -
Daniel Mack