From: Jon Hunter <jonathanh@nvidia.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, "Rob Herring" <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: <linux-sound@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, Jon Hunter <jonathanh@nvidia.com>
Subject: [PATCH 0/3] ASoC: dt-bindings: realtek,rt5640: Various fixes
Date: Thu, 8 Jan 2026 14:31:55 +0000 [thread overview]
Message-ID: <20260108143158.351223-1-jonathanh@nvidia.com> (raw)
This series includes fixes for the realtek,rt5640 dt-binding to address
a few warnings that are observed when running the CHECK_DTBS=y for some
DTBs that use this codec.
Jon Hunter (3):
ASoC: dt-bindings: realtek,rt5640: Document mclk
ASoC: dt-bindings: realtek,rt5640: Update jack-detect
ASoC: dt-bindings: realtek,rt5640: Document port node
.../devicetree/bindings/sound/realtek,rt5640.yaml | 13 +++++++++++++
1 file changed, 13 insertions(+)
--
2.43.0
next reply other threads:[~2026-01-08 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 14:31 Jon Hunter [this message]
2026-01-08 14:31 ` [PATCH 1/3] ASoC: dt-bindings: realtek,rt5640: Document mclk Jon Hunter
2026-01-09 8:50 ` Krzysztof Kozlowski
2026-01-08 14:31 ` [PATCH 2/3] ASoC: dt-bindings: realtek,rt5640: Update jack-detect Jon Hunter
2026-01-09 8:54 ` Krzysztof Kozlowski
2026-01-08 14:31 ` [PATCH 3/3] ASoC: dt-bindings: realtek,rt5640: Document port node Jon Hunter
2026-01-09 8:55 ` Krzysztof Kozlowski
2026-01-13 17:51 ` [PATCH 0/3] ASoC: dt-bindings: realtek,rt5640: Various fixes Mark Brown
2026-01-14 11:27 ` Jon Hunter
2026-01-14 12:03 ` Mark Brown
2026-01-14 22:06 ` Mark Brown
2026-01-17 0:58 ` Thierry Reding
2026-01-21 1:35 ` Rob Herring
2026-01-22 12:21 ` Thierry Reding
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=20260108143158.351223-1-jonathanh@nvidia.com \
--to=jonathanh@nvidia.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-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
/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