From: Shreyas NC <shreyas.nc@intel.com>
To: alsa-devel@alsa-project.org
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
broonie@kernel.org, ckeepax@opensource.cirrus.com,
Shreyas NC <shreyas.nc@intel.com>
Subject: [PATCH v5 0/3] ASoC: Add Multi CPU DAI support
Date: Tue, 22 May 2018 16:10:20 +0530 [thread overview]
Message-ID: <1526985623-2606-1-git-send-email-shreyas.nc@intel.com> (raw)
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 v5:
- Addressed review comments from Charles in calculating delays,
soc_pcm_init_runtime_hw() and other nits
- rebased on latest for-next branch
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 | 6 +
sound/soc/soc-core.c | 280 ++++++++++++++++++++---------
sound/soc/soc-dapm.c | 71 +++++---
sound/soc/soc-pcm.c | 489 ++++++++++++++++++++++++++++++++++-----------------
4 files changed, 574 insertions(+), 272 deletions(-)
--
2.7.4
next reply other threads:[~2018-05-22 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 10:40 Shreyas NC [this message]
2018-05-22 10:40 ` [PATCH v5 1/3] ASoC: Add initial support for multiple CPU DAIs Shreyas NC
2018-05-23 21:38 ` Pierre-Louis Bossart
2018-05-24 5:34 ` Shreyas NC
2018-05-24 20:45 ` Pierre-Louis Bossart
2018-05-25 2:16 ` Shreyas NC
2018-05-22 10:40 ` [PATCH v5 2/3] ASoC: Add multiple CPU DAI support for PCM ops Shreyas NC
2018-05-23 9:22 ` Charles Keepax
2018-05-24 21:29 ` Pierre-Louis Bossart
2018-05-25 4:46 ` Shreyas NC
2018-05-22 10:40 ` [PATCH v5 3/3] ASoC: Add multiple CPU DAI support in DAPM Shreyas NC
2018-05-24 21:37 ` 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=1526985623-2606-1-git-send-email-shreyas.nc@intel.com \
--to=shreyas.nc@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@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).