From: Sheetal <sheetal@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: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
"Thierry Reding" <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mohan Kumar <mkumard@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>, <linux-sound@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Sheetal <sheetal@nvidia.com>
Subject: [PATCH 0/2] ASoC: tegra: Add Tegra268 AHUB support
Date: Wed, 4 Nov 2026 11:20:53 +0000 [thread overview]
Message-ID: <20261104112055.1101243-1-sheetal@nvidia.com> (raw)
Tegra268 has fewer AHUB interfaces than Tegra264: five RX and five TX
ADMAIF interfaces, five I2S instances, two MVC instances, and one each
of AMX, ADX, MIXER and ASRC.
Add the binding and SoC data with DAI, widget, route and mux tables
matching this topology, so the driver exposes the supported audio paths
and uses the Tegra268 register ranges and source masks.
Anupama Kunkulagunta (2):
dt-bindings: sound: Add Tegra268 AHUB support
ASoC: tegra: AHUB: Add Tegra268 support
.../bindings/sound/nvidia,tegra210-ahub.yaml | 1 +
sound/soc/tegra/tegra210_ahub.c | 347 ++++++++++++++++++
sound/soc/tegra/tegra210_ahub.h | 27 ++
3 files changed, 375 insertions(+)
--
2.43.0
next reply other threads:[~2026-11-04 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:20 Sheetal [this message]
2026-11-04 11:20 ` [PATCH 1/2] dt-bindings: sound: " Sheetal
2026-11-05 0:21 ` Mark Brown
2026-11-04 11:20 ` [PATCH 2/2] ASoC: tegra: AHUB: Add Tegra268 support Sheetal
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=20261104112055.1101243-1-sheetal@nvidia.com \
--to=sheetal@nvidia.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=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@kernel.org \
--cc=tiwai@suse.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®