From: Garlic Tseng <garlic.tseng@mediatek.com>
To: broonie@kernel.org, tiwai@suse.de
Cc: alsa-devel@alsa-project.org, ir.lian@mediatek.com,
srv_heupstream@mediatek.com, garlic.tseng@mediatek.com,
linux-kernel@vger.kernel.org, koro.chen@mediatek.com,
linux-mediatek@lists.infradead.org, PC.Liao@mediatek.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ASoC: Mediatek: add MT2701 platform and machine driver
Date: Mon, 4 Jul 2016 18:56:24 +0800 [thread overview]
Message-ID: <1467629788-14411-1-git-send-email-garlic.tseng@mediatek.com> (raw)
Some patches of the patchset "ASoC: Mediatek: Add support for MT2701 SOC"
have been applied to the broonie tree, so I send a new patchset for the
remaining patches.
The patchset adds mt2701 support based on Mediatek AFE common structure.
Change since the previous patchset:
* remove unnecessary set_clkdiv and set_fmt ops in mt2701 platform driver
* add another snd_soc_dai_driver for bt-sco codec to support 8k and 16k
Garlic Tseng (4):
ASoC: mediatek: add mt2701 platform driver implementation.
ASoC: bt-sco: extend rate and add a general compatible string
ASoC: mediatek: add BT implementation
ASoC: mediatek: Add mt2701-cs42448 driver and config option.
Documentation/devicetree/bindings/sound/bt-sco.txt | 2 +-
sound/soc/codecs/bt-sco.c | 52 +-
sound/soc/mediatek/Kconfig | 21 +
sound/soc/mediatek/Makefile | 1 +
sound/soc/mediatek/mt2701/Makefile | 19 +
sound/soc/mediatek/mt2701/mt2701-afe-common.h | 9 -
sound/soc/mediatek/mt2701/mt2701-afe-pcm.c | 1654 ++++++++++++++++++++
sound/soc/mediatek/mt2701/mt2701-cs42448.c | 412 +++++
8 files changed, 2144 insertions(+), 26 deletions(-)
create mode 100644 sound/soc/mediatek/mt2701/Makefile
create mode 100644 sound/soc/mediatek/mt2701/mt2701-afe-pcm.c
create mode 100644 sound/soc/mediatek/mt2701/mt2701-cs42448.c
--
1.9.1
next reply other threads:[~2016-07-04 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 10:56 Garlic Tseng [this message]
[not found] ` <1467629788-14411-1-git-send-email-garlic.tseng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2016-07-04 10:56 ` [alsa-devel] [PATCH 1/4] ASoC: mediatek: add mt2701 platform driver implementation Garlic Tseng
2016-07-04 14:49 ` Applied "ASoC: mediatek: add mt2701 platform driver implementation." to the asoc tree Mark Brown
2016-07-04 10:56 ` [alsa-devel] [PATCH 2/4] ASoC: bt-sco: extend rate and add a general compatible string Garlic Tseng
2016-07-04 14:49 ` Applied "ASoC: bt-sco: extend rate and add a general compatible string" to the asoc tree Mark Brown
2016-07-04 10:56 ` [alsa-devel] [PATCH 3/4] ASoC: mediatek: add BT implementation Garlic Tseng
2016-07-04 14:44 ` Mark Brown
2016-07-05 1:52 ` Garlic Tseng
2016-07-05 8:12 ` [alsa-devel] " Mark Brown
2016-07-05 8:59 ` Garlic Tseng
2016-07-05 9:55 ` Applied "ASoC: mediatek: add BT implementation" to the asoc tree Mark Brown
2016-07-04 10:56 ` [alsa-devel] [PATCH 4/4] ASoC: mediatek: Add mt2701-cs42448 driver and config option Garlic Tseng
2016-07-04 14:49 ` Applied "ASoC: mediatek: Add mt2701-cs42448 driver and config option." to the asoc tree 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=1467629788-14411-1-git-send-email-garlic.tseng@mediatek.com \
--to=garlic.tseng@mediatek.com \
--cc=PC.Liao@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ir.lian@mediatek.com \
--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=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).