From: Jiaxin Yu <jiaxin.yu@mediatek.com>
To: <broonie@kernel.org>, <robh+dt@kernel.org>,
<nfraprado@collabora.com>, <tzungbi@google.com>
Cc: <angelogioacchino.delregno@collabora.com>, <aaronyu@google.com>,
<matthias.bgg@gmail.com>, <trevor.wu@mediatek.com>,
<linmq006@gmail.com>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Jiaxin Yu <jiaxin.yu@mediatek.com>
Subject: [v9 0/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s
Date: Wed, 6 Apr 2022 18:05:10 +0800 [thread overview]
Message-ID: <20220406100514.11269-1-jiaxin.yu@mediatek.com> (raw)
The series reuses mt8192-mt6359-rt1015-rt5682.c for supporting machine
driver with rt1015p speaker amplifier and rt5682s headset codec.
Changes from v8:
- fix typos.
Changes from v7:
- "mediatek,hdmi-codec" is an optional property, the code and the
binding document should match.
Changes from v6:
- "speaker-codec" changes to "speaker-codecs" due to there may be two
speaker codec.
Changes from v5:
- "mediatek,headset-codec" and "mediatek,speaker-codec" drop prefix
and move to properties from patternProperties.
Changes form v4:
- split a large patch into three small patches for easy reviewing
- correct coding style
Changes from v3:
- fix build error: too many arguments for format
[-Werror-format-extra-args]
Changes from v2:
- fix build warnings such as "data argument not used by format string"
Changes from v1:
- uses the snd_soc_of_get_dai_link_codecs to complete the
configuration of dai_link's codecs
- uses definitions to simplifies card name and compatible name
Jiaxin Yu (4):
ASoC: dt-bindings: mt8192-mt6359: add new compatible and new
properties
ASoC: mediatek: mt8192: refactor for I2S3 DAI link of speaker
ASoC: mediatek: mt8192: refactor for I2S8/I2S9 DAI links of headset
ASoC: mediatek: mt8192: support rt1015p_rt5682s
.../sound/mt8192-mt6359-rt1015-rt5682.yaml | 32 +++
sound/soc/mediatek/Kconfig | 1 +
.../mt8192/mt8192-mt6359-rt1015-rt5682.c | 199 +++++++++++-------
3 files changed, 153 insertions(+), 79 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-06 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 10:05 Jiaxin Yu [this message]
2022-04-06 10:05 ` [v9 1/4] ASoC: dt-bindings: mt8192-mt6359: add new compatible and new properties Jiaxin Yu
2022-04-07 22:10 ` Nícolas F. R. A. Prado
2022-04-06 10:05 ` [v9 2/4] ASoC: mediatek: mt8192: refactor for I2S3 DAI link of speaker Jiaxin Yu
2022-04-07 0:56 ` Tzung-Bi Shih
2022-04-07 21:24 ` Nícolas F. R. A. Prado
2022-04-08 3:43 ` Jiaxin Yu
2022-04-06 10:05 ` [v9 3/4] ASoC: mediatek: mt8192: refactor for I2S8/I2S9 DAI links of headset Jiaxin Yu
2022-04-07 21:33 ` Nícolas F. R. A. Prado
2022-04-06 10:05 ` [v9 4/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s Jiaxin Yu
2022-04-07 22:03 ` Nícolas F. R. A. Prado
2022-04-08 14:47 ` [v9 0/4] " 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=20220406100514.11269-1-jiaxin.yu@mediatek.com \
--to=jiaxin.yu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=aaronyu@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linmq006@gmail.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=nfraprado@collabora.com \
--cc=robh+dt@kernel.org \
--cc=trevor.wu@mediatek.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).