From: Daniel Mack <zonque@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: Connecting two Codecs to the same CPU DAI
Date: Tue, 16 Jul 2013 18:33:39 +0200 [thread overview]
Message-ID: <51E575E3.3040409@gmail.com> (raw)
In-Reply-To: <20130716162043.GS22506@sirena.org.uk>
On 16.07.2013 18:20, Mark Brown wrote:
> On Tue, Jul 16, 2013 at 04:31:01PM +0200, Daniel Mack wrote:
>
>> This is cumbersome of course, and I wonder how the core could be
>> augmented in order to handle such cases correctly. Ideally, it should
>> only expose one PCM interface and handle a list of Codecs in the back.
>
>> Or am I unaware of an existing feature?
>
> No, no feature here. Off the top of my head I'd suggest soc-pcm plus a
> virtual DAI for the second link.
That would still require userspace to open and configure both
subdevices, right?
Do you think it's a good idea to teach DAI links support for more than
one codec? At a glance, it seems quite possible: the modes and rates
would be limited down to the intersection of those of each codec, and
the PCM callbacks would be relayed to all codecs in the list.
Thanks,
Daniel
next prev parent reply other threads:[~2013-07-16 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 14:31 Connecting two Codecs to the same CPU DAI Daniel Mack
2013-07-16 16:20 ` Mark Brown
2013-07-16 16:33 ` Daniel Mack [this message]
2013-07-16 16:57 ` Mark Brown
2013-07-16 17:07 ` Daniel Mack
2013-07-16 17:47 ` Mark Brown
2013-07-17 9:16 ` Daniel Mack
2013-07-17 9:31 ` 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=51E575E3.3040409@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.