From: Diogo Ivo <diogo.ivo@bootlin.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>,
Animesh Agarwal <animeshagarwal28@gmail.com>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Diogo Ivo <diogo.ivo@bootlin.com>
Subject: [PATCH 0/2] rt5677: add mclk to DT binding and define it for Smaug
Date: Thu, 03 Sep 2026 00:10:59 +0200 [thread overview]
Message-ID: <20260903-rt5677-mclk-v1-0-b71a5a3533f9@bootlin.com> (raw)
The RT5677 codec has an mclk input that can be fed by an externally
provided clock signal. This small series adds this to the existing
device tree binding and defines the clock that is connected to it
in the specific case of Smaug.
Signed-off-by: Diogo Ivo <diogo.ivo@bootlin.com>
---
Diogo Ivo (2):
ASoC: dt-bindings: realtek,rt5677: Add clock property
arm64: tegra: smaug: Add rt5677 mclk input
Documentation/devicetree/bindings/sound/realtek,rt5677.yaml | 10 ++++++++++
arch/arm64/boot/dts/nvidia/tegra210-smaug.dts | 2 ++
2 files changed, 12 insertions(+)
---
base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
change-id: 20260903-rt5677-mclk-f3ad74db43e1
Best regards,
--
Diogo Ivo <diogo.ivo@bootlin.com>
next reply other threads:[~2026-09-02 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 22:10 Diogo Ivo [this message]
2026-09-02 22:11 ` [PATCH 1/2] ASoC: dt-bindings: realtek,rt5677: Add clock property Diogo Ivo
2026-09-03 9:57 ` Mark Brown
2026-09-03 13:26 ` Diogo Ivo
2026-09-03 21:01 ` Mark Brown
2026-09-04 9:06 ` Diogo Ivo
2026-09-02 22:11 ` [PATCH 2/2] arm64: tegra: smaug: Add rt5677 mclk input Diogo Ivo
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=20260903-rt5677-mclk-v1-0-b71a5a3533f9@bootlin.com \
--to=diogo.ivo@bootlin.com \
--cc=animeshagarwal28@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@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