From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: pierre-louis.bossart@linux.jf.intel.com,
alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: RFC: support for 12 & 24Khz
Date: Sun, 28 Jul 2013 17:54:07 +0530 [thread overview]
Message-ID: <20130728122407.GC1986@intel.com> (raw)
In-Reply-To: <s5hob9p7q7e.wl%tiwai@suse.de>
On Fri, Jul 26, 2013 at 09:09:09AM +0200, Takashi Iwai wrote:
> Relying only on SNDRV_PCM_RATE_* bits doesn't scale.
> What if more other rates are needed at the next time?
Agreed, this is my thinking as well. Remove the usage of macro and use raw rate
values...
~Vinod
--
next prev parent reply other threads:[~2013-07-28 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 17:26 RFC: support for 12 & 24Khz Vinod Koul
2013-07-25 6:45 ` David Henningsson
2013-07-25 15:32 ` Vinod Koul
2013-07-25 6:50 ` Clemens Ladisch
2013-07-25 15:45 ` Vinod Koul
2013-07-25 16:31 ` Takashi Iwai
2013-07-26 6:09 ` Vinod Koul
2013-07-26 7:09 ` Takashi Iwai
2013-07-28 12:24 ` Vinod Koul [this message]
2013-07-25 19:36 ` Mark Brown
2013-07-26 6:11 ` Vinod Koul
2013-07-26 7:10 ` Takashi Iwai
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=20130728122407.GC1986@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=pierre-louis.bossart@linux.jf.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).