From: Mark Brown <broonie@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: jiada_wang@mentor.com, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH 1/1] ASoC: soc-pcm: DPCM cares BE channel constraint
Date: Tue, 26 Jun 2018 15:18:37 +0100 [thread overview]
Message-ID: <20180626141837.GF1779@sirena.org.uk> (raw)
In-Reply-To: <1530014920.2900.50.camel@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Tue, Jun 26, 2018 at 02:08:40PM +0200, Jerome Brunet wrote:
> From comment here and in other mails, I get that you are not big fan of DPCM :)
> It is indeed a complex beast ...
> It there anything else we can use to represent audio routing within the SoC ?
> The SoC I'm working on make heavy use of this, unfortunately.
The goal is to be able to propagate digital configuration along audio
paths in much the same way as we currently do for power with DAPM. Lars
did a presentation with a good writeup of a proposal for that at ELC-E a
few years ago. Unfortunately the only person that is really able to
find time to work on this at the minute is Morimoto-san, this is what
his componentization changes are driving towards - part of the design is
that everything in the system will be a component and we can therefore
treat every device identically.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-06-26 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 9:25 jiada_wang
2018-06-22 14:57 ` Applied "ASoC: soc-pcm: DPCM cares BE channel constraint" to the asoc tree Mark Brown
2018-06-26 10:18 ` [alsa-devel] [PATCH 1/1] ASoC: soc-pcm: DPCM cares BE channel constraint Jerome Brunet
2018-06-26 11:55 ` Mark Brown
2018-06-26 12:08 ` Jerome Brunet
2018-06-26 14:18 ` Mark Brown [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=20180626141837.GF1779@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jbrunet@baylibre.com \
--cc=jiada_wang@mentor.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®