Re: [PATCH 1/6] dt-bindings: iommu: Add Translation Buffer Unit bindings
From: Robin Murphy
Date: Tue Oct 24 2023 - 18:36:47 EST
On 2023-10-24 19:42, Rob Herring wrote:
On Wed, Oct 18, 2023 at 07:19:18PM -0700, Georgi Djakov wrote:
The "apps_smmu" on the Qualcomm sdm845 platform is an implementation
of the ARM SMMU-500, that consists of a single TCU (Translation Control
Unit) and multiple TBUs (Translation Buffer Units). The TCU is already
being described in the ARM SMMU DT schema. Add also bindings for the
TBUs so that we can describe their properties.
Arm SMMU-500 is an implementation, too. Is QCom's a modified
implementation or you are just the first to want to control TBU
resources?
It's very very modified. The stock MMU-500 has very few
microarchitectural registers[1], they all live within the regular SMMU
address space, are all Secure-only by default, and don't do anything
like the shenanigans here.
That said, looking at patch #3, I don't really understand why we need
any of this stuff upstream... AFAICS it's doing an insane amount of work
to use complicated imp-def debug functionality to duplicate things that
the main driver can already do far more efficiently. Sure, in general it
seems like it could potentially be useful stuff for bringing up and
debugging a new driver, but the Linux SMMUv2 driver is mature and
frankly already closer to being obsolete than to being new...
[ digression since I can't be bothered to split this discussion by
replying separately to patch #3: ]
I mean, just looking at qsmmuv500_iova_to_phys(), you do realise that
that's going to be called potentially multiple times by iommu-dma for
*every* dma_sync and dma_unmap call and really wants to be fast, right?
This brings to mind all the work I did a couple of years back[2] because
strict TLB invalidation on unmap was considered too slow for certain
devices on QCom platforms by ChromeOS, yet what this achieves looks like
it could easily be up to an order of magnitude slower again :(
You need to split this into what could be any SMMU-500 implementation
and what is truly QCom specific (i.e. modified). Unlike some licensed IP
that's a free-for-all on DT resources, Arm IP has public specs so we
don't have to guess.
In this DT schema, the TBUs are modelled as a child devices of the TCU
and each of them is described with it's own resources such as clocks,
power domains, interconnects etc.
Signed-off-by: Georgi Djakov <quic_c_gdjako@xxxxxxxxxxx>
---
.../devicetree/bindings/iommu/arm,smmu.yaml | 13 ++++
.../bindings/iommu/qcom,qsmmuv500-tbu.yaml | 67 +++++++++++++++++++
2 files changed, 80 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iommu/qcom,qsmmuv500-tbu.yaml
diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
index cf29ab10501c..afc323b4bbc5 100644
--- a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
+++ b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
@@ -230,6 +230,19 @@ properties:
enabled for any given device.
$ref: /schemas/types.yaml#/definitions/phandle
+ '#address-cells':
+ const: 2
+
+ '#size-cells':
+ const: 2
+
+ ranges: true
+
+patternProperties:
+ "^tbu@[0-9a-f]+$":
+ $ref: qcom,qsmmuv500-tbu.yaml
Generic SMMU binding includes something QCom specific. That's not right.
+ description: The SMMU may include Translation Buffer Units (TBU) as subnodes
+
required:
- compatible
- reg
diff --git a/Documentation/devicetree/bindings/iommu/qcom,qsmmuv500-tbu.yaml b/Documentation/devicetree/bindings/iommu/qcom,qsmmuv500-tbu.yaml
new file mode 100644
index 000000000000..4baba7397e90
--- /dev/null
+++ b/Documentation/devicetree/bindings/iommu/qcom,qsmmuv500-tbu.yaml
@@ -0,0 +1,67 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iommu/qcom,qsmmuv500-tbu.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Qualcomm TBU (Translation Buffer Unit)
+
+maintainers:
+ - Georgi Djakov <quic_c_gdjako@xxxxxxxxxxx>
+
+description:
+ TBU nodes represent Translation Buffer Units in an ARM SMMU. Each TBU node
+ should be a child node of the SMMU in the device tree.
+
+properties:
+ compatible:
+ enum:
+ - qcom,qsmmuv500-tbu
+
+ reg:
+ items:
+ - description: Address and size of the TBU's register space.
+
+ reg-names:
+ items:
+ - const: base
+
+ clocks:
+ maxItems: 1
+
+ interconnects:
+ maxItems: 1
What does this interconnect represent? MMU-500 TBUs don't access memory
themselves[3], they only have an internal AXI Stream interface to the
TCU to request translations.
Thanks,
Robin.
[1]
https://developer.arm.com/documentation/ddi0517/f/programmers-model/memory-model
[2]
https://lore.kernel.org/all/d652966348c78457c38bf18daf369272a4ebc2c9.1628682049.git.robin.murphy@xxxxxxx/
[3] Yeah yeah, other than the special case of TBU0 issuing pagetable
walks on behalf of the TCU when it's not configured with its own
dedicated PTW interface, I know :P
+
+ power-domains:
+ maxItems: 1
+
+ qcom,stream-id-range:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ description: Stream ID range (address and size) that is assigned by the TBU
+
+required:
+ - compatible
+ - reg
+ - interconnects
+ - qcom,stream-id-range
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/clock/qcom,gcc-sdm845.h>
+ #include <dt-bindings/interconnect/qcom,sdm845.h>
+ #include <dt-bindings/power/qcom-rpmpd.h>
+
+
+ tbu@150e1000 {
+ compatible = "qcom,qsmmuv500-tbu";
+ reg = <0x150e1000 0x1000>;
+ reg-names = "base";
+ clocks = <&gcc GCC_AGGRE_NOC_PCIE_TBU_CLK>;
+ power-domains = <&gcc HLOS1_VOTE_AGGRE_NOC_MMU_PCIE_TBU_GDSC>;
+ interconnects = <&system_noc MASTER_GNOC_SNOC 0 &config_noc SLAVE_IMEM_CFG 0>;
+ qcom,stream-id-range = <0x1c00 0x400>;
+ };
+
+...