From: Fei Shao <fshao@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: Fei Shao <fshao@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh@kernel.org>,
Steve Lee <steves.lee@maximintegrated.com>,
Trevor Wu <trevor.wu@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-sound@vger.kernel.org
Subject: [PATCH 0/4] Update properties in two ASoC DT bindings
Date: Fri, 25 Oct 2024 18:44:40 +0800 [thread overview]
Message-ID: <20241025104548.1220076-1-fshao@chromium.org> (raw)
Hi maintainers,
This series includes four patches to update two ASoC DT bindings. The
goal is to fix dtbs_check warnings found with DAI links and audio
routing configuration on some MediaTek SoCs (MT8195 and MT8188).
This series doesn't introduce new properties - all are either commonly
described in existing bindings or are available but undocumented.
Patches 1 and 2 focus on mediatek,mt8188-mt6359.yaml, adding two
vendor-specific properties and updating the DAI link pattern to be more
generic.
Patches 3 and 4 focus on maxim,max98390.yaml, referencing
dai-common.yaml and documenting a hidden vendor-specific property.
Regards,
Fei
Fei Shao (4):
ASoC: dt-bindings: mediatek,mt8188-mt6359: Add adsp and dai-link
properties
ASoC: dt-bindings: mediatek,mt8188-mt6359: Update DAI link node
pattern
ASoC: dt-bindings: maxim,max98390: Refernce common DAI properties
ASoC: dt-bindings: maxim,max98390: Document maxim,dsm_param_name
property
.../devicetree/bindings/sound/maxim,max98390.yaml | 9 ++++++++-
.../bindings/sound/mediatek,mt8188-mt6359.yaml | 14 ++++++++++++--
2 files changed, 20 insertions(+), 3 deletions(-)
--
2.47.0.163.g1226f6d8fa-goog
next reply other threads:[~2024-10-25 10:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 10:44 Fei Shao [this message]
2024-10-25 10:44 ` [PATCH 1/4] ASoC: dt-bindings: mediatek,mt8188-mt6359: Add adsp and dai-link properties Fei Shao
2024-10-27 20:54 ` Krzysztof Kozlowski
2024-10-28 11:10 ` Fei Shao
2024-10-28 14:25 ` AngeloGioacchino Del Regno
2024-10-29 3:04 ` Trevor Wu (吳文良)
2024-10-29 8:52 ` Fei Shao
2024-10-25 10:44 ` [PATCH 2/4] ASoC: dt-bindings: mediatek,mt8188-mt6359: Update DAI link node pattern Fei Shao
2024-10-27 20:56 ` Krzysztof Kozlowski
2024-10-28 11:12 ` Fei Shao
2024-10-29 6:26 ` Krzysztof Kozlowski
2024-10-25 10:44 ` [PATCH 3/4] ASoC: dt-bindings: maxim,max98390: Refernce common DAI properties Fei Shao
2024-10-27 20:55 ` Krzysztof Kozlowski
2024-10-28 11:14 ` Fei Shao
2024-10-25 10:44 ` [PATCH 4/4] ASoC: dt-bindings: maxim,max98390: Document maxim,dsm_param_name property Fei Shao
2024-10-27 20:59 ` Krzysztof Kozlowski
2024-10-28 11:14 ` Fei Shao
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=20241025104548.1220076-1-fshao@chromium.org \
--to=fshao@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=steves.lee@maximintegrated.com \
--cc=trevor.wu@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;
as well as URLs for NNTP newsgroup(s).