From: "Wang, Sen" <sen@ti.com>
To: "Shah, Moteen" <m-shah@ti.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"Menon, Nishanth" <nm@ti.com>,
"Raghavendra, Vignesh" <vigneshr@ti.com>,
"kristo@kernel.org" <kristo@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kumar, Udit" <u-kumar1@ti.com>,
"Gujulan Elango, Hari Prasath" <gehariprasath@ti.com>,
"Abhilash Chandra, Yemike" <y-abhilashchandra@ti.com>
Subject: Re: [PATCH v6 2/2] arm64: dts: ti: Add audio overlay for k3-j721s2-evm
Date: Sun, 21 Jun 2026 22:52:05 -0500 [thread overview]
Message-ID: <62e07989-f0b2-4346-bee8-5d7a11f4ea44@ti.com> (raw)
In-Reply-To: <20260619062749.1575066-3-m-shah@ti.com>
On 6/19/2026 1:27 AM, Shah, Moteen wrote:
> From: Jayesh Choudhary <j-choudhary@ti.com>
>
> Add device tree overlay to enable analog audio support on J721S2-EVM
> using PCM3168A codec connected to McASP4 serializers.
>
> - Add audio_refclk1 clock node to k3-j721s2-main.dtsi
> - Add nodes for sound-card, audio codec, I2C3 and McASP4
> - Add pinmux for I2C3, McASP4, AUDIO_EXT_REFCLK1 and WKUP_GPIO_0
> - Add GPIO expander (TCA6408) for codec control
> - Add GPIO hogs to route I2C3 lines and McASP serializers
> - Set idle-state to 0 in mux0 and mux1 for McASP signal routing
>
Hi Moteen, thanks for the patch.
Reviewed-by: Sen Wang <sen@ti.com>
prev parent reply other threads:[~2026-06-22 3:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 6:27 [PATCH v6 0/2] Enable audio support for J721S2 EVM Moteen Shah
2026-06-19 6:27 ` [PATCH v6 1/2] dt-bindings: ti: Update audio-refclk binding and j721e system controller Moteen Shah
2026-07-13 10:07 ` Vignesh Raghavendra
2026-06-19 6:27 ` [PATCH v6 2/2] arm64: dts: ti: Add audio overlay for k3-j721s2-evm Moteen Shah
2026-06-22 3:52 ` Wang, Sen [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=62e07989-f0b2-4346-bee8-5d7a11f4ea44@ti.com \
--to=sen@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gehariprasath@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-shah@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=y-abhilashchandra@ti.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
all inboxes | Powered by JetHome®