From: Jon Hunter <jonathanh@nvidia.com>
To: Sheetal <sheetal@nvidia.com>, 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>,
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
Subject: Re: [PATCH 0/2] ASoC: tegra: Add Tegra268 ADMAIF support
Date: Thu, 12 Nov 2026 12:10:13 +0000 [thread overview]
Message-ID: <8a065e1a-7e80-428d-b3f2-7dafd445184e@nvidia.com> (raw)
In-Reply-To: <20261104111836.1100527-1-sheetal@nvidia.com>
On 04/11/2026 11:18, Sheetal wrote:
> Tegra268 reuses the Tegra264 ADMAIF register layout but provides only
> five RX and five TX interfaces. Add its binding, SoC data, DAI and
> control tables, and FIFO defaults to match this configuration.
>
> Anupama Kunkulagunta (2):
> dt-bindings: sound: Add Tegra268 ADMAIF support
> ASoC: tegra: ADMAIF: Add Tegra268 support
>
> .../sound/nvidia,tegra210-admaif.yaml | 22 +++++++
> sound/soc/tegra/tegra210_admaif.c | 66 +++++++++++++++++++
> sound/soc/tegra/tegra210_admaif.h | 20 ++++++
> 3 files changed, 108 insertions(+)
>
For the series ...
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Thanks
Jon
--
nvpublic
prev parent reply other threads:[~2026-11-12 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:18 [PATCH 0/2] ASoC: tegra: Add Tegra268 ADMAIF support Sheetal
2026-11-04 11:18 ` [PATCH 1/2] dt-bindings: sound: " Sheetal
2026-11-04 11:23 ` sashiko-bot
2026-11-04 11:18 ` [PATCH 2/2] ASoC: tegra: ADMAIF: Add Tegra268 support Sheetal
2026-11-12 14:20 ` Mark Brown
2026-11-12 12:10 ` Jon Hunter [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=8a065e1a-7e80-428d-b3f2-7dafd445184e@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-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=sheetal@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.