alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Can DAPM paths span multiple codecs/drivers?
Date: Fri, 05 Apr 2013 15:21:09 +0200	[thread overview]
Message-ID: <515ECFC5.5060703@topic.nl> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433ED4049D@DBDE01.ent.ti.com>

If two codecs need each other for certain operations, is there a way to 
define DAPM links between them?

For example, codec A has an analog input "x". It can route this input 
via some output pin to an input of codec B. (In other words, A could be 
a codec that provides an SPDIF output and B could be a codec that can 
only handle digital inputs like the SPDIF from codec A).

Now codec B can record from input "x", but to do so, it would have to 
activate a path leading through codec A. (hence, codec A will need to be 
a bit active)

I have a suspicion that this is possible by hand-crafting some of the 
dapm structs and linking them together. Before I try, I would like to 
know if there's even a possiblity that this will work from folks more 
knowledgable on this topic.

My current implementation is to tell DAPM that i have an "always 
enabled" ADC path and just do everything myself. Which is of course 
wasteful.

Mike.

  reply	other threads:[~2013-04-05 13:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 16:38 [PATCH v2] davinci-mcasp: Add support for multichannel playback Michal Bachraty
2013-03-05 11:06 ` Bedia, Vaibhav
2013-03-05 11:41   ` Michal Bachraty
2013-03-05 12:03     ` Bedia, Vaibhav
2013-03-05 12:24       ` Michal Bachraty
2013-03-05 16:01   ` Daniel Mack
2013-03-06 10:54     ` Bedia, Vaibhav
2013-03-06 10:57       ` Mark Brown
2013-03-06 11:19         ` Bedia, Vaibhav
2013-03-08  7:29           ` Mike Looijmans
2013-03-11  7:01             ` Bedia, Vaibhav
2013-03-11  8:33               ` Mike Looijmans
2013-03-11  8:56                 ` Bedia, Vaibhav
2013-04-05 13:21                   ` Mike Looijmans [this message]
2013-04-10 11:08                   ` Mike Looijmans
2013-03-06 11:00       ` Daniel Mack
2013-03-06 11:19         ` Bedia, Vaibhav
2013-03-08 14:22           ` Mike Looijmans
2013-03-11  7:01             ` Bedia, Vaibhav
2013-03-06 14:27       ` Michal Bachraty
2013-03-06 14:31         ` Bedia, Vaibhav
2013-03-06 14:44     ` Michal Bachraty
2013-03-07 11:59       ` Bedia, Vaibhav
2013-03-08 13:11   ` Daniel Mack

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=515ECFC5.5060703@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=alsa-devel@alsa-project.org \
    /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).