From: Qiao Zhou <zhouqiao@marvell.com>
To: Mark Brown <broonie@kernel.org>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [DAPM question] DAPM support for single input multiple outputs
Date: Tue, 10 Mar 2015 09:56:41 +0800 [thread overview]
Message-ID: <54FE4F59.4060906@marvell.com> (raw)
In-Reply-To: <20150309122055.GI28806@sirena.org.uk>
On 03/09/2015 08:20 PM, Mark Brown wrote:
> Not really - it's not that there's any reason not to do it, it's just
> that nobody is doing the work as far as I know. It's quite unusual to
> see it in hardware (usually you see mixers in the places where you might
> see a demux) so few people have the motivation to do the work.
Understood and I agree that it is rare. Thanks for clarifying.
--
Best Regards
Qiao
prev parent reply other threads:[~2015-03-10 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 8:38 [DAPM question] DAPM support for single input multiple outputs Qiao Zhou
2015-03-09 8:53 ` Lars-Peter Clausen
2015-03-09 11:16 ` Qiao Zhou
2015-03-09 12:20 ` Mark Brown
2015-03-10 1:56 ` Qiao Zhou [this message]
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=54FE4F59.4060906@marvell.com \
--to=zhouqiao@marvell.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=tiwai@suse.de \
/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