From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [alsa-devel] Question about DPCM FE vs BE
Date: Wed, 9 Oct 2019 21:20:06 -0500 [thread overview]
Message-ID: <70a91c94-3c4d-6f78-7a71-bb8bdbc28b6a@linux.intel.com> (raw)
In-Reply-To: <87pnj57a2w.wl-kuninori.morimoto.gx@renesas.com>
>> It is my understanding that the current code would not support a case
>> where a FE is also a BE.
>>
>> That said, do we want to preclude it? at some point we probably want
>> to get rid of the FE/BE distinction and have 'domains' that can be
>> chained. So it may not be a good thing to cast a restriction in
>> stone. If at some point we need a list of upstream/downstream clients
>> maybe we should keep this.
>
> Yeah, "domains" is nice idea !!
>
> But, before that, I think we need to cleanup soc-pcm.
> I'm reading it, but it is too much complex, and too unreadable...
> I want to cleanup it first. I believe it can help
> the conversion (= FE/BE to domains).
The idea of domains/constraint propagation is not mine BTW, it was
presented by Lars some 2-3 years ago. there may be a note somewhere in
the audio miniconference minutes.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-10 2:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 7:57 [alsa-devel] Question about DPCM FE vs BE Kuninori Morimoto
2019-10-09 14:20 ` Pierre-Louis Bossart
2019-10-09 23:50 ` Kuninori Morimoto
2019-10-10 2:20 ` Pierre-Louis Bossart [this message]
2019-10-10 2:38 ` Kuninori Morimoto
2019-10-10 14:07 ` 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=70a91c94-3c4d-6f78-7a71-bb8bdbc28b6a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.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