From: "Thierry Reding" <thierry.reding@gmail.com>
To: "Svyatoslav Ryhel" <clamor95@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Andre Przywara" <andre.przywara@arm.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Romain Perier" <romain.perier@gmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Robert Eckelmann" <longnoserob@gmail.com>
Cc: <devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] ARM: tegra: nexus7: add missing clock binding into sound node
Date: Thu, 22 Feb 2024 18:18:49 +0100 [thread overview]
Message-ID: <CZBS2E10TRA3.23RY1MDLKZCD4@gmail.com> (raw)
In-Reply-To: <20240129181049.89971-2-clamor95@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On Mon Jan 29, 2024 at 7:10 PM CET, Svyatoslav Ryhel wrote:
> From: Robert Eckelmann <longnoserob@gmail.com>
>
> A recent rt5640 codec update requires mclk definition in the
> device tree. Without mclk defined sound will not work.
>
> Signed-off-by: Robert Eckelmann <longnoserob@gmail.com>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
> .../boot/dts/nvidia/tegra30-asus-nexus7-grouper-common.dtsi | 3 +++
> 1 file changed, 3 insertions(+)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-22 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 18:10 [PATCH v1 0/1] Tegra30: fix sound on Nexus 7 Svyatoslav Ryhel
2024-01-29 18:10 ` [PATCH v1 1/1] ARM: tegra: nexus7: add missing clock binding into sound node Svyatoslav Ryhel
2024-02-22 17:18 ` Thierry Reding [this message]
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=CZBS2E10TRA3.23RY1MDLKZCD4@gmail.com \
--to=thierry.reding@gmail.com \
--cc=andre.przywara@arm.com \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=longnoserob@gmail.com \
--cc=mani@kernel.org \
--cc=robh+dt@kernel.org \
--cc=romain.perier@gmail.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).