From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Bard liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
pierre-louis.bossart@linux.intel.com,
liam.r.girdwood@linux.intel.com, broonie@kernel.org,
bard.liao@intel.com
Subject: Re: [alsa-devel] [PATCH RFC v2 0/4] ASoC: Add Multi CPU DAI support
Date: 15 Jan 2020 15:11:03 +0900 [thread overview]
Message-ID: <87tv4xjll4.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20200114175152.3291-1-yung-chuan.liao@linux.intel.com>
Hi Bard
> As discussed in [1], ASoC core supports multi codec DAIs
> on a DAI link. However it does not do so for CPU DAIs.
>
> So, add support for multi CPU DAIs on a DAI Link by adding
> multi CPU DAI in Card instantiation, suspend and resume
> functions, PCM ops, stream handling functions and DAPM.
>
> [1]: https://www.spinics.net/lists/alsa-devel/msg71369.html
>
> changes in v2:
> - rebase on asoc-next
> - fix some typo
> - compare and merge Kuninori Morimoto's version
> - add warning if the function is not support multi cpu yet
>
> Bard liao (1):
> ASoC: add warning if the function is not support multi cpu yet.
>
> Shreyas NC (3):
> ASoC: Add initial support for multiple CPU DAIs
> ASoC: Add multiple CPU DAI support for PCM ops
> ASoC: Add multiple CPU DAI support in DAPM
>
> include/sound/soc.h | 15 +
> sound/soc/soc-compress.c | 7 +-
> sound/soc/soc-core.c | 222 ++++++-----
> sound/soc/soc-dapm.c | 131 +++---
> sound/soc/soc-generic-dmaengine-pcm.c | 12 +
> sound/soc/soc-pcm.c | 547 +++++++++++++++++---------
> 6 files changed, 599 insertions(+), 335 deletions(-)
Thank you for merging my version !!
Thank you for your help !!
Best regards
---
Kuninori Morimoto
_______________________________________________
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-15 6:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 17:51 [alsa-devel] [PATCH RFC v2 0/4] ASoC: Add Multi CPU DAI support Bard liao
2020-01-14 17:51 ` [alsa-devel] [PATCH RFC v2 1/4] ASoC: Add initial support for multiple CPU DAIs Bard liao
2020-01-14 17:51 ` [alsa-devel] [PATCH RFC v2 2/4] ASoC: Add multiple CPU DAI support for PCM ops Bard liao
2020-01-16 1:48 ` Pierre-Louis Bossart
2020-01-16 2:05 ` Liao, Bard
2020-01-16 2:25 ` Pierre-Louis Bossart
2020-01-14 17:51 ` [alsa-devel] [PATCH RFC v2 3/4] ASoC: Add multiple CPU DAI support in DAPM Bard liao
2020-01-14 17:51 ` [alsa-devel] [PATCH RFC v2 4/4] ASoC: add warning if the function is not support multi cpu yet Bard liao
2020-01-16 1:49 ` Pierre-Louis Bossart
2020-01-16 7:42 ` Liao, Bard
2020-01-17 0:45 ` Kuninori Morimoto
2020-01-15 6:11 ` Kuninori Morimoto [this message]
2020-01-15 22:13 ` [alsa-devel] [PATCH RFC v2 0/4] ASoC: Add Multi CPU DAI support Pierre-Louis Bossart
2020-01-16 0:47 ` Kuninori Morimoto
2020-01-16 1:20 ` Pierre-Louis Bossart
2020-01-16 1:52 ` Pierre-Louis Bossart
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=87tv4xjll4.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).