From: Daniel Mack <daniel@caiaq.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Wrong sample rate user space -> kernel space?
Date: Tue, 7 Jul 2009 17:24:57 +0200 [thread overview]
Message-ID: <20090707152457.GO19257@buzzloop.caiaq.de> (raw)
In-Reply-To: <4A536548.70300@ladisch.de>
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
prev parent reply other threads:[~2009-07-07 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 14:29 Wrong sample rate user space -> kernel space? Daniel Mack
2009-07-07 15:10 ` Clemens Ladisch
2009-07-07 15:24 ` Daniel Mack [this message]
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=20090707152457.GO19257@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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