From: PC Liao <pc.liao@mediatek.com>
To: broonie@kernel.org, tiwai@suse.de
Cc: alsa-devel@alsa-project.org, srv_heupstream@mediatek.com,
s.hauer@pengutronix.de, linux-kernel@vger.kernel.org,
koro.chen@mediatek.com, linux-mediatek@lists.infradead.org,
PC Liao <pc.liao@mediatek.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2 v6] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver
Date: Wed, 20 Apr 2016 14:40:45 +0800 [thread overview]
Message-ID: <1461134447-42001-1-git-send-email-pc.liao@mediatek.com> (raw)
Because applied patch (commit 0beeb8d0b434b8b007ac8058fb2cac5997fff6df
"ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver") is
dropped, I upload new version which include dependent patch.
Changes since v5:
- add "ASoC: core: export snd_soc_get_dai_name" patch.
Because snd_soc_of_get_dai_name() fix the property name "sound-dai".
Our patch needs to change name to use, so export
snd_soc_get_dai_name() which is included in snd_soc_of_get_dai_name().
Changes since v4:
Change name from "sound-dai" to "capture-dai" to determine the capture path
Changes since v2,v3:
Fix unclear code and use sound-dai to determine the capture path
Changes since v1:
Use codec dai name to determine the capture path.
Jean-Francois Moine (1):
ASoC: core: export snd_soc_get_dai_name
PC Liao (1):
ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver
.../devicetree/bindings/sound/mt8173-rt5650.txt | 6 +++
include/sound/soc.h | 2 +
sound/soc/mediatek/mt8173-rt5650.c | 44 ++++++++++++++++++--
sound/soc/soc-core.c | 5 ++-
4 files changed, 52 insertions(+), 5 deletions(-)
--
1.7.9.5
next reply other threads:[~2016-04-20 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 6:40 PC Liao [this message]
2016-04-20 6:40 ` [PATCH 1/2 v6] ASoC: core: export snd_soc_get_dai_name PC Liao
2016-04-20 6:40 ` [PATCH 2/2 v6] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver PC Liao
2016-04-20 8:29 ` Mark Brown
2016-04-20 9:39 ` PC Liao
2016-04-20 16:11 ` Mark Brown
2016-04-20 13:30 ` Matthias Brugger
2016-04-20 16:27 ` PC Liao
2016-04-21 9:22 ` Matthias Brugger
2016-04-21 9:38 ` PC Liao
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=1461134447-42001-1-git-send-email-pc.liao@mediatek.com \
--to=pc.liao@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=koro.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=srv_heupstream@mediatek.com \
--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).