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: [PATCH RFC v4 0/6] ASoC: Add Multi CPU DAI support
Date: Tue, 25 Feb 2020 01:56:58 +0000 [thread overview]
Message-ID: <20200225015658.GB21366@sirena.org.uk> (raw)
In-Reply-To: <20200120132928.25257-1-yung-chuan.liao@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
On Mon, Jan 20, 2020 at 09:29:22PM +0800, Bard Liao wrote:
> As discussed in [1], ASoC core supports multi codec DAIs
> on a DAI link. However it does not do so for CPU DAIs.
Sorry, I didn't apply this at -rc1 like I intended to and now it
needs some rebasing - can you resend please? My mistake, sorry.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-25 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 13:29 [alsa-devel] [PATCH RFC v4 0/6] ASoC: Add Multi CPU DAI support Bard Liao
2020-01-20 13:29 ` [alsa-devel] [PATCH RFC v4 1/6] ASoC: Add initial support for multiple CPU DAIs Bard Liao
2020-01-20 13:29 ` [alsa-devel] [PATCH RFC v4 2/6] ASoC: Add multiple CPU DAI support for PCM ops Bard Liao
2020-01-20 13:29 ` [alsa-devel] [PATCH RFC v4 3/6] ASoC: Add dapm_add_valid_dai_widget helper Bard Liao
2020-01-20 13:29 ` [alsa-devel] [PATCH RFC v4 4/6] ASoC: Add multiple CPU DAI support in DAPM Bard Liao
2020-01-20 13:29 ` [alsa-devel] [PATCH RFC v4 5/6] ASoC: return error if the function is not support multi cpu yet Bard Liao
2020-01-20 13:29 ` [alsa-devel] [PATCH RFC v4 6/6] ASoC: pcm: check if cpu DAI support the given stream Bard Liao
2020-01-22 16:57 ` [alsa-devel] [PATCH RFC v4 0/6] ASoC: Add Multi CPU DAI support Mark Brown
2020-02-25 1:56 ` Mark Brown [this message]
2020-02-25 2:54 ` 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=20200225015658.GB21366@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox