From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [alsa-devel] Question about DPCM FE vs BE
Date: Thu, 10 Oct 2019 15:07:19 +0100 [thread overview]
Message-ID: <20191010140719.GU2036@sirena.org.uk> (raw)
In-Reply-To: <87lftt72ad.wl-kuninori.morimoto.gx@renesas.com>
[-- Attachment #1.1: Type: text/plain, Size: 803 bytes --]
On Thu, Oct 10, 2019 at 11:38:34AM +0900, Kuninori Morimoto wrote:
> > 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.
> Yes, I guess it was ELC-E.
> My work (*) is to helpping him/his idea.
> (*) No categorize CPU/Codec/Platfrom
> modern style dai_link
> soc-core / soc-pcm cleanup (on going)
> (Semi) multi CPU support (will post)
> (Semi) no categorize CPU/Codec DAI (will post)
I just dug the talk Lars did up the other day funnily enough:
https://elinux.org/images/e/e7/Audio_on_Linux.pdf
https://www.youtube.com/watch?v=6oQF2TzCYtQ
I'd posted something similar as well, the main issue is someone
getting the time to actually work on it :/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2019-10-10 14:08 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
2019-10-10 2:38 ` Kuninori Morimoto
2019-10-10 14:07 ` 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=20191010140719.GU2036@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=pierre-louis.bossart@linux.intel.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