From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: alsa-devel@alsa-project.org, Trent Piepho <tpiepho@gmail.com>,
Omair Mohammed Abdullah <omair.m.abdullah@linux.intel.com>,
Ramesh Babu <ramesh.babu@intel.com>,
lrg@ti.com
Subject: Re: ASoC:Question rate constraint between the dais
Date: Sun, 18 Mar 2012 21:27:11 +0000 [thread overview]
Message-ID: <20120318212710.GA3074@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CABb+yY1-tG9Mj9D13Kj3-M9ykEndwWijR8NOG8-TA-5Y+-jxUA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 857 bytes --]
On Sun, Mar 18, 2012 at 11:52:01AM +0530, Jassi Brar wrote:
> Implementation wise, maybe two tightly coupled dais at machine level,
> could be represented as one virtual dai with independent virtual 'mute'
> switches for each physical path?
When I've considered implementing this in the past I've thought about
doing something like having DAI groups which own the physical link
configuration when you've got more than one logical link on the same
physical infrastructure. The physical configuration would then get
punted up to the group level and we'd need some mechanism for the group
to start clocks when required.
I've only ever thought about it though so there may be some problems
there I've not come up with yet. Might be useful to start the
refactoring for the clocks anyway, might be useful for the
reconfigurable channel allocation cases too.
[-- 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-18 21:27 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
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 [this message]
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=20120318212710.GA3074@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jassisinghbrar@gmail.com \
--cc=lrg@ti.com \
--cc=omair.m.abdullah@linux.intel.com \
--cc=ramesh.babu@intel.com \
--cc=tpiepho@gmail.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).