From: Timur Tabi <timur@freescale.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: How do I tell ALSA that my driver supports every possible sample rate?
Date: Tue, 24 Jul 2007 14:30:29 -0500 [thread overview]
Message-ID: <46A65355.4040101@freescale.com> (raw)
In-Reply-To: <s5hd4yhyh5n.wl%tiwai@suse.de>
Takashi Iwai wrote:
>> #define SNDRV_PCM_RATE_ALL (SNDRV_PCM_RATE_8000_192000 | SNDRV_PCM_RATES_5512)
>
> I'd prefer 5512_19200. The word "ALL" may vary in future.
That's the point. It's supposed to indicate all sample rates no matter what they are or
will be. However, that may be a moot point ...
> Anyway, the bits SND_PCM_RATES_[0-9]* are ignored when _CONTINUOUS or
> _KNOT is passed. Only the values in rate_min/rate_max fields are
> referred as actual min/max rates.
Ah! I wish this stuff were documented in the source files.
So can I do this?
static const struct snd_pcm_hardware mpc86xx_pcm_hardware = {
.rates = SNDRV_PCM_RATE_CONTINUOUS,
.rate_min = 1,
.rate_max = (unsigned int) -1,
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-07-24 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 15:54 How do I tell ALSA that my driver supports every possible sample rate? Timur Tabi
2007-07-23 16:39 ` Liam Girdwood
2007-07-23 17:06 ` Timur Tabi
2007-07-23 17:29 ` Liam Girdwood
2007-07-23 17:14 ` Clemens Ladisch
2007-07-23 17:27 ` Timur Tabi
2007-07-24 7:14 ` Clemens Ladisch
2007-07-24 14:54 ` Timur Tabi
2007-07-24 15:07 ` Takashi Iwai
2007-07-24 19:30 ` Timur Tabi [this message]
2007-07-25 10:18 ` Takashi Iwai
2007-07-25 14:37 ` Timur Tabi
2007-07-25 15:08 ` Takashi Iwai
2007-07-25 15:12 ` Takashi Iwai
2007-07-25 15:24 ` Liam Girdwood
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=46A65355.4040101@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.