[PATCH v2 1/4] dt-bindings: iommu: arm,smmu-v3: Allow a clock and a reset

From: Arun Iyengar via B4 Relay

Date: Thu Nov 12 2026 - 03:26:22 EST


From: Arun Iyengar <aiyengar1990@xxxxxxxxx>

Some SoCs feed the SMMUv3 from a clock that the OS controls. On the
Rockchip RK3588 the MMU-600 for PCIe runs from ACLK_MMU_PCIE, whose only
other consumers are the PCIe controllers. When no PCIe controller is
enabled, the clock framework gates it as unused, and the SMMU can no
longer be accessed. The same SMMU also has a reset line in the CRU,
SRST_A_MMU_PCIE.

Allow a single clock and a single reset, so that both can be described.
The architecture defines no clock or reset inputs; the MMU-600 TRM lists
one clock and one reset signal, and the one integration that needs this
has one of each. An implementation with more clocks or resets can add
them with names and a specific compatible.

Link: https://support.arm.com/documentation/100310/0202/Signal-descriptions/Clock-and-reset-signals
Signed-off-by: Arun Iyengar <aiyengar1990@xxxxxxxxx>
---
Documentation/devicetree/bindings/iommu/arm,smmu-v3.yaml | 11 +++++++++++
1 file changed, 11 insertions(+)

diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu-v3.yaml b/Documentation/devicetree/bindings/iommu/arm,smmu-v3.yaml
index 3c044e4f03d4..29b81b4fb650 100644
--- a/Documentation/devicetree/bindings/iommu/arm,smmu-v3.yaml
+++ b/Documentation/devicetree/bindings/iommu/arm,smmu-v3.yaml
@@ -63,6 +63,17 @@ properties:

msi-parent: true

+ clocks:
+ maxItems: 1
+ description:
+ Clock of the SMMU's register and memory interfaces, on SoCs where the
+ OS has to keep it running.
+
+ resets:
+ maxItems: 1
+ description:
+ Reset of the SMMU, on SoCs where it is controlled by the OS.
+
nvidia,cmdqv:
description: |
A phandle to its pairing CMDQV extension for an implementation on NVIDIA

--
2.55.0