Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	ALSA development <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Requiring the same sample rate for playback and	record?
Date: Wed, 16 Jul 2008 16:17:48 +0100	[thread overview]
Message-ID: <1216221468.6734.5.camel@odin> (raw)
In-Reply-To: <487E0F9F.1060401@freescale.com>

On Wed, 2008-07-16 at 10:11 -0500, Timur Tabi wrote:
> Takashi Iwai wrote:
> 
> > In a simple case, you don't need hw_constraint functions.  Just
> > override the corresponding fields of runtime->hw in open callback.
> > 
> > For example, pci/via82xx.c sets the current rate value to
> > runtime->hw.rate_min/max if there is another stream.
> 
> Are you talking about this code:
> 
> 	} else {
> 		/* a fixed rate */
> 		runtime->hw.rates = SNDRV_PCM_RATE_KNOT;
> 		runtime->hw.rate_max = runtime->hw.rate_min = ratep->rate;
> 	}
> 
> Last I heard, ASoC doesn't work with SNDRV_PCM_RATE_KNOT.  But I think I can
> still use this method.  I'll just need to use a real SNDRV_PCM_RATE_xxx value.
> 

Supporting KNOT in the core is probably the best solution. It shouldn't
be too hard at add ....

Liam

  reply	other threads:[~2008-07-16 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 19:08 Requiring the same sample rate for playback and record? Timur Tabi
2008-06-23 11:00 ` Takashi Iwai
2008-06-23 12:08   ` Timur Tabi
2008-06-23 12:10     ` Takashi Iwai
2008-07-14 21:25   ` Timur Tabi
2008-07-16 10:59     ` Takashi Iwai
2008-07-16 15:11       ` Timur Tabi
2008-07-16 15:17         ` Liam Girdwood [this message]
2008-07-16 15:24         ` Takashi Iwai
2008-07-16 19:19       ` Timur Tabi
2008-07-17 10:10         ` Takashi Iwai
2008-07-25 19:55           ` Timur Tabi

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=1216221468.6734.5.camel@odin \
    --to=lg@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=timur@freescale.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