From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Simon <horms@verge.net.au>, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: ASoC: How to mix multi input ?
Date: Wed, 20 May 2015 19:13:06 +0100 [thread overview]
Message-ID: <20150520181306.GP21577@sirena.org.uk> (raw)
In-Reply-To: <87pp5v3jz9.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]
On Wed, May 20, 2015 at 05:20:06AM +0000, Kuninori Morimoto wrote:
> I would like to ask you how to mix multi input in ASoC.
> Renesas sound device(s) can mix multi input to 1 output.
You mean in DPCM rather than a plain CODEC?
> Here, sound A/B/C will be used randomly.
> Does ALSA SoC already has this kind of system ?
I *think* at least the Intel systems do this already.
> My image about these are like this.
> sound A: aplay -D hw:0 ...
> sound B: aplay -D hw:1 ...
> sound C: aplay -D hw:2 ...
> ...
> codec will be started if one of A/B/C are started,
> and it will be stopped if all of A/B/C are stopped.
If you connect multiple front ends to one back end this should work
(with DAPM routes and so on). If it doesn't work then that's something
that should work.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-05-20 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 5:20 ASoC: How to mix multi input ? Kuninori Morimoto
2015-05-20 18:13 ` Mark Brown [this message]
2015-05-21 0:20 ` Kuninori Morimoto
2015-05-21 11:05 ` Mark Brown
2015-05-22 0:01 ` Kuninori Morimoto
2015-05-22 17:59 ` Liam Girdwood
2015-05-22 18:04 ` Mark Brown
2015-05-25 5:48 ` Vinod Koul
2015-05-25 8:06 ` Kuninori Morimoto
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=20150520181306.GP21577@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--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.