Received: by 2002:a05:7412:8598:b0:f9:33c2:5753 with SMTP id n24csp575538rdh; Tue, 19 Dec 2023 07:26:54 -0800 (PST) X-Google-Smtp-Source: AGHT+IGZQCUfSjUuE5UbWj97aYK/zRgVNqtpI9e6xmy969+3jYAho8x2A9Pg4jU2yaru+68HgyQL X-Received: by 2002:a05:6a20:3d8f:b0:18c:3ea9:b85d with SMTP id s15-20020a056a203d8f00b0018c3ea9b85dmr1382515pzi.11.1702999614269; Tue, 19 Dec 2023 07:26:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702999614; cv=none; d=google.com; s=arc-20160816; b=hnfE2USfTd8/DM2Lcq2vsZ8hItcd6BO3hcgHUqpMTksbf95Zp4EA8wmQ1XS2nuuqE7 SgtpW6uG1LxOPGlio7fs2+aOHtAq1J0bPChJT0A7GATXiKWmPbuZq8IFz9ntTsFFwBJH S+mVO0Wi65IDXe0iozrcSiC9g9lO9ZxsdF7mDBa6iajW41CRys+JQcNoJA2WVkW4/m8d DEk9edxZusEcFsqxfIyyn11b2SgAePDgF+QRBTC9tz9Dy95juHEqMYyCt1D4ObSLbioM BDlHMhMb0BrdjLoMHoUUc9lKW7WvvdQC7lhLNR8//W+DxiWpE1Wn7yeP8NA3bPOS9jC+ 4Ang== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:date:message-id; bh=mJWT9+BR1p6vSl5shDS1je7Vp7OIOFwni6A56Wqwx38=; fh=lPdYCffYa2kja6sl796ETVFWrfzP/IK4SS7omTYI3sw=; b=wt9wie6uKCpvN2nvayODKJJl4fRA8s7TsAB+/+VNYOxq4GufkGIiA0hfV8XQ6GN4VP FsvCyCnC3yRlaR2+cPediE+wU+C9HEyNoEP+nP3NT1ZOaSELVL462VZVG8pNjVrvbabU lfwv+opn33zTcu2JgZO26nJtBpTN4hqQ1FGU4yRBtlwkr4vrzWJRLO0fKTr99eAQFpDW C99qL7B1Scp4W5jsrGiRN5D6MNKsWTSbG/0zLANiETs+gRoyKpH2AB/5421VaBdWFfS1 PrrfRrGpfHajzzGv/bwxzpmGBxCu3MzQI02p5k+Y0JCr8peBb26snshokUCvreSl9M2Q vcDg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel+bounces-5483-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-5483-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id bx2-20020a056a02050200b005c1739564f7si20155080pgb.351.2023.12.19.07.26.54 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 Dec 2023 07:26:54 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-5483-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel+bounces-5483-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-5483-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 57848283C5D for ; Tue, 19 Dec 2023 15:26:00 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id D71491D54C; Tue, 19 Dec 2023 15:25:28 +0000 (UTC) X-Original-To: linux-kernel@vger.kernel.org Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 724CA1C6B2; Tue, 19 Dec 2023 15:25:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 11FBE1FB; Tue, 19 Dec 2023 07:26:06 -0800 (PST) Received: from [10.57.85.119] (unknown [10.57.85.119]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B84953F738; Tue, 19 Dec 2023 07:25:19 -0800 (PST) Message-ID: Date: Tue, 19 Dec 2023 15:25:19 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v5] dt-bindings: iommu: Convert msm,iommu-v0 to yaml Content-Language: en-GB To: David Heidelberg , Joerg Roedel , Will Deacon , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Andy Gross , Bjorn Andersson , Konrad Dybcio Cc: iommu@lists.linux.dev, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org References: <20231216002242.112310-2-david@ixit.cz> From: Robin Murphy In-Reply-To: <20231216002242.112310-2-david@ixit.cz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2023-12-16 12:22 am, David Heidelberg wrote: > Convert Qualcomm IOMMU v0 implementation to yaml format. > > Signed-off-by: David Heidelberg > --- > v5: > - updated example (thx @Konrad) > - ordering of requirements + dropped > and | and reformatted (thx @Konrad) > v4: > - renamed to qcom,apq8064-iommu as Rob requested > - changed title to Qualcomm APQ8064 IOMMU > - dropped quotes around URLs > - dropped mdp node > - dropped unused mdp_port0 label > > v3: > - I kept the name as -v0, since we have other binding -v1 and it look > good, I can change thou in v4 if requested. > - dropped non-existent smmu_clk part (and adjusted example, which was > using it) > - dropped iommu description > - moved iommu-cells description to the property #iommu-cells > > v2: > - fix wrong path in binding $id > - comment qcom,mdp4 node example (we don't want to validate it yet) > > .../bindings/iommu/msm,iommu-v0.txt | 64 --------------- > .../bindings/iommu/qcom,apq8064-iommu.yaml | 82 +++++++++++++++++++ > 2 files changed, 82 insertions(+), 64 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/iommu/msm,iommu-v0.txt > create mode 100644 Documentation/devicetree/bindings/iommu/qcom,apq8064-iommu.yaml > > diff --git a/Documentation/devicetree/bindings/iommu/msm,iommu-v0.txt b/Documentation/devicetree/bindings/iommu/msm,iommu-v0.txt > deleted file mode 100644 > index 20236385f26e..000000000000 > --- a/Documentation/devicetree/bindings/iommu/msm,iommu-v0.txt > +++ /dev/null > @@ -1,64 +0,0 @@ > -* QCOM IOMMU > - > -The MSM IOMMU is an implementation compatible with the ARM VMSA short > -descriptor page tables. It provides address translation for bus masters outside > -of the CPU, each connected to the IOMMU through a port called micro-TLB. > - > -Required Properties: > - > - - compatible: Must contain "qcom,apq8064-iommu". > - - reg: Base address and size of the IOMMU registers. > - - interrupts: Specifiers for the MMU fault interrupts. For instances that > - support secure mode two interrupts must be specified, for non-secure and > - secure mode, in that order. For instances that don't support secure mode a > - single interrupt must be specified. > - - #iommu-cells: The number of cells needed to specify the stream id. This > - is always 1. > - - qcom,ncb: The total number of context banks in the IOMMU. > - - clocks : List of clocks to be used during SMMU register access. See > - Documentation/devicetree/bindings/clock/clock-bindings.txt > - for information about the format. For each clock specified > - here, there must be a corresponding entry in clock-names > - (see below). > - > - - clock-names : List of clock names corresponding to the clocks specified in > - the "clocks" property (above). > - Should be "smmu_pclk" for specifying the interface clock > - required for iommu's register accesses. > - Should be "smmu_clk" for specifying the functional clock > - required by iommu for bus accesses. > - > -Each bus master connected to an IOMMU must reference the IOMMU in its device > -node with the following property: > - > - - iommus: A reference to the IOMMU in multiple cells. The first cell is a > - phandle to the IOMMU and the second cell is the stream id. > - A single master device can be connected to more than one iommu > - and multiple contexts in each of the iommu. So multiple entries > - are required to list all the iommus and the stream ids that the > - master is connected to. > - > -Example: mdp iommu and its bus master > - > - mdp_port0: iommu@7500000 { > - compatible = "qcom,apq8064-iommu"; > - #iommu-cells = <1>; > - clock-names = > - "smmu_pclk", > - "smmu_clk"; > - clocks = > - <&mmcc SMMU_AHB_CLK>, > - <&mmcc MDP_AXI_CLK>; > - reg = <0x07500000 0x100000>; > - interrupts = > - , > - ; > - qcom,ncb = <2>; > - }; > - > - mdp: qcom,mdp@5100000 { > - compatible = "qcom,mdp"; > - ... > - iommus = <&mdp_port0 0 > - &mdp_port0 2>; > - }; > diff --git a/Documentation/devicetree/bindings/iommu/qcom,apq8064-iommu.yaml b/Documentation/devicetree/bindings/iommu/qcom,apq8064-iommu.yaml > new file mode 100644 > index 000000000000..5af59305d277 > --- /dev/null > +++ b/Documentation/devicetree/bindings/iommu/qcom,apq8064-iommu.yaml > @@ -0,0 +1,82 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > + > +$id: http://devicetree.org/schemas/iommu/qcom,apq8064-iommu.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Qualcomm APQ8064 IOMMU > + > +maintainers: > + - Will Deacon > + > +description: > + The MSM IOMMU is an implementation compatible with the ARM VMSA short > + descriptor page tables. It provides address translation for bus masters > + outside of the CPU, each connected to the IOMMU through a port called micro-TLB. > + > +properties: > + compatible: > + const: qcom,apq8064-iommu > + > + clocks: > + items: > + - description: interface clock for register accesses > + - description: functional clock for bus accesses > + > + clock-names: > + items: > + - const: smmu_pclk > + - const: iommu_clk > + > + reg: > + maxItems: 1 > + > + interrupts: > + description: Specifiers for the MMU fault interrupts. > + minItems: 1 > + items: > + - description: non-secure mode interrupt > + - description: secure mode interrupt (for instances which supports it) > + > + "#iommu-cells": > + const: 1 > + description: > + The first cell is a phandle to the IOMMU and the second cell > + is the stream id. > + A single master device can be connected to more than one iommu > + and multiple contexts in each of the iommu. > + So multiple entries are required to list all the iommus and > + the stream ids that the master is connected to. This seems pretty confusing since it's the description for some other property, not this one. FWIW I'd just put this as something like "Each IOMMU specifier describes a single Stream ID.", and if you think it's really worth calling out that clients can have multiple IOMMU specifiers, I'd stick that in the overall description. Thanks, Robin. > + > + qcom,ncb: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: The total number of context banks in the IOMMU. > + > +required: > + - reg > + - interrupts > + - clocks > + - clock-names > + - qcom,ncb > + > +additionalProperties: false > + > +examples: > + - | > + #include > + #include > + #include > + > + iommu@7500000 { > + compatible = "qcom,apq8064-iommu"; > + reg = <0x07500000 0x100000>; > + interrupts = , > + ; > + clocks = <&clk SMMU_AHB_CLK>, > + <&clk MDP_AXI_CLK>; > + clock-names = "smmu_pclk", > + "iommu_clk"; > + #iommu-cells = <1>; > + qcom,ncb = <2>; > + };