From: Nicolin Chen <nicoleotsuka@gmail.com>
To: <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com, tiwai@suse.de,
b42378@freescale.com, b02247@freescale.com,
linux-kernel@vger.kernel.org, timur@tabi.org,
Li.Xiubo@freescale.com, perex@perex.cz,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/4] ASoC: fsl: Add stream names to CPU DAI drivers for DPCM
Date: Wed, 30 Jul 2014 11:10:25 +0800 [thread overview]
Message-ID: <cover.1406688048.git.nicoleotsuka@gmail.com> (raw)
DPCM needs extra dapm routes in the machine driver to route audio
between Front-End and Back-End. In order to differ the stream names
in the route map from CODECs, we here add specific stream names to
all Freescale ASoC CPU DAI drivers so that we can implement ASRC via
DPCM to each of them.
Document for DPCM: ./Documentation/sound/alsa/soc/DPCM.txt
Nicolin Chen (4):
ASoC: fsl_esai: Add stream names for DPCM usage
ASoC: fsl_sai: Add stream names for DPCM usage
ASoC: fsl_spdif: Add stream names for DPCM usage
ASoC: fsl_ssi: Add stream names for DPCM usage
sound/soc/fsl/fsl_esai.c | 2 ++
sound/soc/fsl/fsl_sai.c | 2 ++
sound/soc/fsl/fsl_spdif.c | 2 ++
sound/soc/fsl/fsl_ssi.c | 2 ++
4 files changed, 8 insertions(+)
--
1.8.4
next reply other threads:[~2014-07-30 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 3:10 Nicolin Chen [this message]
2014-07-30 3:10 ` [PATCH 1/4] ASoC: fsl_esai: Add stream names for DPCM usage Nicolin Chen
2014-07-30 3:10 ` [PATCH 2/4] ASoC: fsl_sai: " Nicolin Chen
2014-07-30 3:10 ` [PATCH 3/4] ASoC: fsl_spdif: " Nicolin Chen
2014-07-30 3:10 ` [PATCH 4/4] ASoC: fsl_ssi: " Nicolin Chen
2014-07-30 12:19 ` Timur Tabi
2014-07-31 19:55 ` [PATCH 0/4] ASoC: fsl: Add stream names to CPU DAI drivers for DPCM Mark Brown
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=cover.1406688048.git.nicoleotsuka@gmail.com \
--to=nicoleotsuka@gmail.com \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=b02247@freescale.com \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=perex@perex.cz \
--cc=timur@tabi.org \
--cc=tiwai@suse.de \
/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).