From: Mark Brown <broonie@kernel.org>
To: Bard liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, kuninori.morimoto.gx@renesas.com,
tiwai@suse.de, pierre-louis.bossart@linux.intel.com,
liam.r.girdwood@linux.intel.com, bard.liao@intel.com
Subject: Re: [alsa-devel] [PATCH RFC 0/3] ASoC: Add Multi CPU DAI support
Date: Tue, 14 Jan 2020 15:47:39 +0000 [thread overview]
Message-ID: <20200114154739.GA3897@sirena.org.uk> (raw)
In-Reply-To: <20191225191501.23848-1-yung-chuan.liao@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 353 bytes --]
On Thu, Dec 26, 2019 at 03:14:58AM +0800, Bard liao wrote:
> From: Bard Liao <yung-chuan.liao@linux.intel.com>
>
> As discussed in [1], ASoC core supports multi codec DAIs
> on a DAI link. However it does not do so for CPU DAIs.
This approach seems broadly fine - I see you'd already agreed
some updates with Morimoto-san which look sensible.
[-- 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
next prev parent reply other threads:[~2020-01-14 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 19:14 [alsa-devel] [PATCH RFC 0/3] ASoC: Add Multi CPU DAI support Bard liao
2019-12-25 19:14 ` [alsa-devel] [PATCH RFC 1/3] ASoC: Add initial support for multiple CPU DAIs Bard liao
2019-12-26 8:16 ` Kuninori Morimoto
2019-12-26 9:15 ` Liao, Bard
2019-12-25 19:15 ` [alsa-devel] [PATCH RFC 2/3] ASoC: Add multiple CPU DAI support for PCM ops Bard liao
2019-12-25 19:15 ` [alsa-devel] [PATCH RFC 3/3] ASoC: Add multiple CPU DAI support in DAPM Bard liao
2020-01-14 15:47 ` Mark Brown [this message]
2020-01-15 0:20 ` [alsa-devel] [PATCH RFC 0/3] ASoC: Add Multi CPU DAI support Liao, Bard
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=20200114154739.GA3897@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@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 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.