From: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
dmaengine@vger.kernel.org (open list:DMA GENERIC OFFLOAD ENGINE
SUBSYSTEM),
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list),
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Niravkumar L Rabara <niravkumar.l.rabara@intel.com>,
linux-mtd@lists.infradead.org (open list:CADENCE NAND DRIVER),
Dinh Nguyen <dinguyen@kernel.org>,
Khairul Anuar Romli <khairul.anuar.romli@altera.com>,
Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
Subject: [PATCH v3 0/3] Add iommu supports
Date: Wed, 15 Oct 2025 08:13:36 +0800 [thread overview]
Message-ID: <cover.1760486497.git.khairul.anuar.romli@altera.com> (raw)
This patch series adds IOMMU support for the Agilex5 platform by:
- Updating the device tree bindings for:
- Cadence HP NAND controller (`cdns,hp-nfc`)
- Synopsys DesignWare AXI DMA controller (`snps,dw-axi-dmac`)
to accept the `iommus` property.
- Adding the SMMU (System Memory Management Unit) node to the Agilex5
device tree and wiring up the IOMMU properties to the supported
peripherals:
- NAND controller
- DMA controller
- SPI controller
The Agilex5 SoC includes an ARM SMMU v3 with dedicated Translation Buffer
Units (TBUs) for peripherals. These allow for hardware-enforced DMA
address translation and memory isolation using the IOMMU framework.
Enabling IOMMU support ensures proper integration of these devices in
virtualized or secure environments, and aligns the platform with ARM’s
architectural requirements.
---
Changes in v3:
- Refined commit messages with detailed hardware descriptions.
- Clarified which peripherals are covered in the DT changes.
Changes in v2:
- Add more description in the commit message body to clarify
device required for this changes.
---
Khairul Anuar Romli (3):
dt-bindings: mtd: cdns,hp-nfc: Add iommu property
dt-bindings: dma: snps,dw-axi-dmac: Add iommu property
arm64: dts: socfpga: agilex5: Add SMMU nodes
.../bindings/dma/snps,dw-axi-dmac.yaml | 3 +++
.../devicetree/bindings/mtd/cdns,hp-nfc.yaml | 3 +++
arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi | 16 ++++++++++++++++
3 files changed, 22 insertions(+)
--
2.35.3
next reply other threads:[~2025-10-15 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 0:13 Khairul Anuar Romli [this message]
2025-10-15 0:13 ` [PATCH v3 1/3] dt-bindings: mtd: cdns,hp-nfc: Add iommu property Khairul Anuar Romli
2025-10-20 10:33 ` Krzysztof Kozlowski
2025-10-15 0:13 ` [PATCH 2/3] dt-bindings: dma: snps,dw-axi-dmac: " Khairul Anuar Romli
2025-10-20 11:09 ` Krzysztof Kozlowski
2025-10-15 0:13 ` [PATCH 3/3] arm64: dts: socfpga: agilex5: Add SMMU nodes Khairul Anuar Romli
2025-10-20 15:22 ` [PATCH v3 0/3] Add iommu supports Dinh Nguyen
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=cover.1760486497.git.khairul.anuar.romli@altera.com \
--to=khairul.anuar.romli@altera.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=adrianhoyin.ng@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=niravkumar.l.rabara@intel.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).