From: "Sheetal ." <sheetal@nvidia.com>
To: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
Marc Zyngier <maz@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
Liam Girdwood <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>, <dmaengine@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-sound@vger.kernel.org>, sheetal <sheetal@nvidia.com>
Subject: [PATCH V2 0/4] Add tegra264 audio device tree support
Date: Mon, 29 Sep 2025 16:29:26 +0530 [thread overview]
Message-ID: <20250929105930.1767294-1-sheetal@nvidia.com> (raw)
From: sheetal <sheetal@nvidia.com>
Add device tree support for tegra264 audio subsystem including:
- Binding update for
- 64-channel ADMA controller
- 32 RX/TX ADMAIF channels
- tegra264-agic binding for arm,gic
- Add device tree nodes for
- APE subsystem (ACONNECT, AGIC, ADMA, AHUB and children (ADMAIF, I2S,
DMIC, DSPK, MVC, SFC, ASRC, AMX, ADX, OPE and Mixer) nodes
- HDA controller
- sound
Note:
The change is dependent on https://patchwork.ozlabs.org/project/linux-tegra/patch/20250818135241.3407180-1-thierry.reding@gmail.com/
...
Changes in V2:
- Update the allOf condition in Patch 2/4.
sheetal (4):
dt-bindings: dma: Update ADMA bindings for tegra264
dt-bindings: sound: Update ADMAIF bindings for tegra264
dt-bindings: interrupt-controller: arm,gic: Add tegra264-agic
arm64: tegra: Add tegra264 audio support
.../bindings/dma/nvidia,tegra210-adma.yaml | 15 +-
.../interrupt-controller/arm,gic.yaml | 1 +
.../sound/nvidia,tegra210-admaif.yaml | 106 +-
.../arm64/boot/dts/nvidia/tegra264-p3971.dtsi | 106 +
arch/arm64/boot/dts/nvidia/tegra264.dtsi | 3190 +++++++++++++++++
5 files changed, 3377 insertions(+), 41 deletions(-)
--
2.34.1
next reply other threads:[~2025-09-29 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 10:59 Sheetal . [this message]
2025-09-29 10:59 ` [PATCH V2 1/4] dt-bindings: dma: Update ADMA bindings for tegra264 Sheetal .
2025-10-30 19:25 ` Thierry Reding
2025-09-29 10:59 ` [PATCH V2 2/4] dt-bindings: sound: Update ADMAIF " Sheetal .
2025-10-06 21:36 ` Rob Herring (Arm)
2025-09-29 10:59 ` [PATCH V2 3/4] dt-bindings: interrupt-controller: arm,gic: Add tegra264-agic Sheetal .
2025-09-29 10:59 ` [PATCH V2 4/4] arm64: tegra: Add tegra264 audio support Sheetal .
2025-10-30 19:24 ` Thierry Reding
2025-09-29 15:28 ` [PATCH V2 0/4] Add tegra264 audio device tree support Rob Herring (Arm)
2025-09-30 6:24 ` Sheetal .
2025-10-07 1:07 ` Krzysztof Kozlowski
2025-10-15 16:22 ` (subset) " Mark Brown
2025-12-23 11:28 ` Vinod Koul
2026-01-16 18:59 ` Thierry Reding
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=20250929105930.1767294-1-sheetal@nvidia.com \
--to=sheetal@nvidia.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--cc=spujar@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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