From: Jiaxin Yu <jiaxin.yu@mediatek.com>
To: <broonie@kernel.org>, <matthias.bgg@gmail.com>,
<robh+dt@kernel.org>, <tiwai@suse.com>,
<linux-kernel@vger.kernel.org>
Cc: alsa-devel@alsa-project.org, shane.chien@mediatek.com,
howie.huang@mediatek.com, Jiaxin Yu <jiaxin.yu@mediatek.com>,
tzungbi@google.com, linux-mediatek@lists.infradead.org,
eason.yen@mediatek.com, bicycle.tsai@mediatek.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/2] Add mediatek codec mt6359 driver
Date: Mon, 17 Aug 2020 14:07:33 +0800 [thread overview]
Message-ID: <1597644455-8216-1-git-send-email-jiaxin.yu@mediatek.com> (raw)
Add mediatek codec (MT6359) driver
MT6359 support playback and capture 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) HP Mux --> "Audio Playback"
v5 changes:
1. Don't need to unregister the component which is already relegated to devm.
v4 changes:
1. Add a remove() function to undo regulator_enable().
2. Removed unnecessary logs.
3. patchwork link:
https://patchwork.kernel.org/cover/11715553/
https://patchwork.kernel.org/patch/11716015/
https://patchwork.kernel.org/patch/11715557/
v3 changes:
1. patchwork link:
https://patchwork.kernel.org/cover/11714291/
https://patchwork.kernel.org/patch/11714295/
https://patchwork.kernel.org/patch/11714339/
v2 changes:
1. patchwork link:
https://patchwork.kernel.org/cover/11706935/
https://patchwork.kernel.org/patch/11708865/
https://patchwork.kernel.org/patch/11706937/
v1 changes:
1.lkml link:
https://lkml.org/lkml/2020/3/5/1257
Jiaxin Yu (2):
ASoC: mediatek: mt6359: add codec driver
dt-bindings: mediatek: mt6359: add codec document
.../devicetree/bindings/sound/mt6359.yaml | 68 +
sound/soc/codecs/Kconfig | 8 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/mt6359.c | 2753 ++++++++++++++++++++
sound/soc/codecs/mt6359.h | 2640 +++++++++++++++++++
5 files changed, 5471 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/mt6359.yaml
create mode 100644 sound/soc/codecs/mt6359.c
create mode 100644 sound/soc/codecs/mt6359.h
--
1.8.1.1.dirty
next reply other threads:[~2020-08-17 6:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 6:07 Jiaxin Yu [this message]
2020-08-17 6:07 ` [PATCH v5 1/2] ASoC: mediatek: mt6359: add codec driver Jiaxin Yu
2020-08-17 7:32 ` Tzung-Bi Shih
2020-08-17 6:07 ` [PATCH v5 2/2] dt-bindings: mediatek: mt6359: add codec document Jiaxin Yu
2020-08-17 7:29 ` Tzung-Bi Shih
2020-08-17 8:11 ` Tzung-Bi Shih
2020-08-19 10:37 ` Mark Brown
2020-08-19 15:42 ` Tzung-Bi Shih
2020-08-19 19:40 ` Mark Brown
2020-09-07 13:37 ` Tzung-Bi Shih
2020-09-07 17:50 ` 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=1597644455-8216-1-git-send-email-jiaxin.yu@mediatek.com \
--to=jiaxin.yu@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=bicycle.tsai@mediatek.com \
--cc=broonie@kernel.org \
--cc=eason.yen@mediatek.com \
--cc=howie.huang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shane.chien@mediatek.com \
--cc=tiwai@suse.com \
--cc=tzungbi@google.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).