From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ramesh Babu <ramesh.babu@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC:Question rate constraint between the dais
Date: Thu, 15 Mar 2012 17:53:11 +0000 [thread overview]
Message-ID: <20120315175310.GR3138@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <64362.10.252.27.21.1331805184.squirrel@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]
On Thu, Mar 15, 2012 at 03:23:04PM +0530, Ramesh Babu wrote:
> I need to make sure that all simultaneous playback and capture (across the
> all dai_links) needs to be of same frequency family.
> If the sampling frequency of a new request is different from ongoing
> playback/capture, then it needs to be rejected.
> How do I handle it in machine driver?
Why do you need to do this in the machine driver? Such a constraint
sounds like it's coming from one of the chips in the system rather than
from the machine itself so it'd seem sensible for the chip itself to
impose the constraint so that other machines don't need to replicate the
code.
See wm8988 for an example of adding sample rate constraints, obviously
you can change the criteria dynamically.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-03-15 17:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 9:53 ASoC:Question rate constraint between the dais Ramesh Babu
2012-03-15 17:53 ` Mark Brown [this message]
2012-03-15 21:28 ` Trent Piepho
2012-03-16 19:25 ` Mark Brown
2012-03-16 20:00 ` Lars-Peter Clausen
2012-03-17 11:41 ` Mark Brown
2012-03-17 13:00 ` Clemens Ladisch
[not found] ` <9DF50024A2F6A5439EBFE2E74F4E9198055254@BGSMSX101.gar.corp.intel.com>
2012-03-16 10:05 ` Omair Mohammed Abdullah
2012-03-16 19:22 ` Mark Brown
2012-03-16 22:01 ` Trent Piepho
2012-03-17 11:48 ` Mark Brown
2012-03-17 19:49 ` Trent Piepho
2012-03-17 20:31 ` Mark Brown
2012-03-18 6:22 ` Jassi Brar
2012-03-18 21:27 ` Mark Brown
2012-03-19 16:12 ` James Courtier-Dutton
2012-03-19 16:32 ` Mark Brown
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=20120315175310.GR3138@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=ramesh.babu@linux.intel.com \
/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).