From: Eason Yen <eason.yen@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: <eason.yen@mediatek.com>, <jiaxin.yu@mediatek.com>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>, <wsd_upstream@mediatek.com>
Subject: [PATCH 0/2] Add mediatek codec mt6359 driver
Date: Fri, 6 Mar 2020 11:33:40 +0800 [thread overview]
Message-ID: <1583465622-16628-1-git-send-email-eason.yen@mediatek.com> (raw)
Add mediatek codec (MT6359) driver
MT6359 support playback, capture and vow feature.
On downlink path, it includes three DACs for handset, headset,
and lineout path. On unlink path, it includeds three ADCs for
main mic, second mic, 3rd mic, and headset mic.
By scenario, select *_MUX widget to create damp path.
And by select mic_type_mux to choose DMIC/AMIC/....
For example, select these MUX widget to create headset path
(1) DAC In Mux --> "Normal Path"
(2) HPL Mux --> "Audio Playback"
(3) HPR Mux --> "Audio Playback"
Eason Yen (2):
ASoC: mediatek: mt6359: add codec document
ASoC: codec: mediatek: add mt6359 codec driver
Documentation/devicetree/bindings/sound/mt6359.txt | 16 +
sound/soc/codecs/Kconfig | 9 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/mt6359.c | 4217 ++++++++++++++++++++
sound/soc/codecs/mt6359.h | 3212 +++++++++++++++
5 files changed, 7456 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/mt6359.txt
create mode 100644 sound/soc/codecs/mt6359.c
create mode 100644 sound/soc/codecs/mt6359.h
--
1.9.1
next reply other threads:[~2020-03-06 3:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 3:33 Eason Yen [this message]
2020-03-06 3:33 ` [PATCH 1/2] ASoC: mediatek: mt6359: add codec document Eason Yen
2020-03-12 19:05 ` Rob Herring
2020-03-06 3:33 ` [PATCH 2/2] ASoC: codec: mediatek: add mt6359 codec driver Eason Yen
2020-03-09 13:13 ` Mark Brown
2020-03-11 9:22 ` Eason Yen
2020-03-11 12:12 ` Mark Brown
2020-03-12 6:43 ` Eason Yen
2020-03-12 19:08 ` 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=1583465622-16628-1-git-send-email-eason.yen@mediatek.com \
--to=eason.yen@mediatek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxin.yu@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=wsd_upstream@mediatek.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