Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp769283imm; Wed, 25 Jul 2018 06:02:06 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdQ38seUpkVrz3yGnAxIGBgmPntBrnREkw9Z70lOidyD3iOb85bnd0NQdzJlGtJZNqhuBsn X-Received: by 2002:a17:902:820a:: with SMTP id x10-v6mr21090292pln.261.1532523726213; Wed, 25 Jul 2018 06:02:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532523726; cv=none; d=google.com; s=arc-20160816; b=WgjRijojR+Kqc/eHoEnaOfFyYBREi7so87H48lvqyeisiF4c6u1saxS2qQrZRzwwSJ N8G97KhK54ZIdafUUhjeA1syWYM3VMi6xJODKQlxwcDiG1BmohUJS4trOrh9eqoG55Xc 6V/X/U8CMzENfZmBL5U401NeRGBC5xe/4hW6DaZBWq5q6TayO44+1oRf/bfC21NFzdQh EGqjfEfEbvy0sKomoFxw8x9X4Ocv840HV9cnfHUigKP5ZMK6cFNsXhiQBCOACuLuOWTr ku9pbVV2As4x2+8rgqXLhhd25vTTrgSxT1Pgs7IvvBGtSaDdPg9fc3cBuQhrXnRHGgpf AnOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=aKFtuprn7yPnOL2H1i9cFcB77T31/Gpy5TDaxMmk74o=; b=jLLcb/XzYUaLAoaXDDDHpFvwalJ2jwK9ywhbDs+KpV/pO8BztplxIec+Hl1MUX7kDJ xkK+16EGbWyhW9w3Ap8zVWdcpJnGB2p2UOToQl/amUJvXu7PqnmM6CQu1Ma8DZ8l9PSm FKpwxoi0LvLDnLQ7uCRktaHyFsW9Axaf0nXrjRpxok/3O6ulQD/WpoW/zO7KDnBydqDR mcCDZrRZ3AZInCByFcyMHNGBk3sqRrRnfPp7m3ZRY8t1e2Nh4RAYQqbPyi5YHFDaqIpT jBZM3a6vKx9bnfgjvwTDFv0ax4U/Pi6ZtLfidcQhElhsSmajzH1pwYkGTyvyDxVqy3dC 9Cng== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d38-v6si14260951pgl.88.2018.07.25.06.01.50; Wed, 25 Jul 2018 06:02:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728968AbeGYOMb (ORCPT + 99 others); Wed, 25 Jul 2018 10:12:31 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:38390 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728476AbeGYOMb (ORCPT ); Wed, 25 Jul 2018 10:12:31 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 86D9380D; Wed, 25 Jul 2018 06:00:55 -0700 (PDT) Received: from [10.4.12.131] (e110467-lin.emea.arm.com [10.4.12.131]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id EDCE03F237; Wed, 25 Jul 2018 06:00:51 -0700 (PDT) Subject: Re: [PATCH 1/7 v6] Documentation: fsl-mc: add iommu-map device-tree binding for fsl-mc bus To: Nipun Gupta , will.deacon@arm.com, robh+dt@kernel.org, robh@kernel.org, mark.rutland@arm.com, catalin.marinas@arm.com, gregkh@linuxfoundation.org, laurentiu.tudor@nxp.com, bhelgaas@google.com, hch@lst.de Cc: joro@8bytes.org, m.szyprowski@samsung.com, shawnguo@kernel.org, frowand.list@gmail.com, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org, bharat.bhushan@nxp.com, stuyoder@gmail.com, leoyang.li@nxp.com References: <1531135103-10699-1-git-send-email-nipun.gupta@nxp.com> <1531135103-10699-2-git-send-email-nipun.gupta@nxp.com> From: Robin Murphy Message-ID: Date: Wed, 25 Jul 2018 14:00:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1531135103-10699-2-git-send-email-nipun.gupta@nxp.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/07/18 12:18, Nipun Gupta wrote: > The existing IOMMU bindings cannot be used to specify the relationship > between fsl-mc devices and IOMMUs. This patch adds a generic binding for > mapping fsl-mc devices to IOMMUs, using iommu-map property. No more nits from me :) Acked-by: Robin Murphy > Signed-off-by: Nipun Gupta > Reviewed-by: Rob Herring > --- > .../devicetree/bindings/misc/fsl,qoriq-mc.txt | 39 ++++++++++++++++++++++ > 1 file changed, 39 insertions(+) > > diff --git a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt b/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt > index 6611a7c..01fdc33 100644 > --- a/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt > +++ b/Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt > @@ -9,6 +9,25 @@ blocks that can be used to create functional hardware objects/devices > such as network interfaces, crypto accelerator instances, L2 switches, > etc. > > +For an overview of the DPAA2 architecture and fsl-mc bus see: > +Documentation/networking/dpaa2/overview.rst > + > +As described in the above overview, all DPAA2 objects in a DPRC share the > +same hardware "isolation context" and a 10-bit value called an ICID > +(isolation context id) is expressed by the hardware to identify > +the requester. > + > +The generic 'iommus' property is insufficient to describe the relationship > +between ICIDs and IOMMUs, so an iommu-map property is used to define > +the set of possible ICIDs under a root DPRC and how they map to > +an IOMMU. > + > +For generic IOMMU bindings, see > +Documentation/devicetree/bindings/iommu/iommu.txt. > + > +For arm-smmu binding, see: > +Documentation/devicetree/bindings/iommu/arm,smmu.txt. > + > Required properties: > > - compatible > @@ -88,14 +107,34 @@ Sub-nodes: > Value type: > Definition: Specifies the phandle to the PHY device node associated > with the this dpmac. > +Optional properties: > + > +- iommu-map: Maps an ICID to an IOMMU and associated iommu-specifier > + data. > + > + The property is an arbitrary number of tuples of > + (icid-base,iommu,iommu-base,length). > + > + Any ICID i in the interval [icid-base, icid-base + length) is > + associated with the listed IOMMU, with the iommu-specifier > + (i - icid-base + iommu-base). > > Example: > > + smmu: iommu@5000000 { > + compatible = "arm,mmu-500"; > + #iommu-cells = <1>; > + stream-match-mask = <0x7C00>; > + ... > + }; > + > fsl_mc: fsl-mc@80c000000 { > compatible = "fsl,qoriq-mc"; > reg = <0x00000008 0x0c000000 0 0x40>, /* MC portal base */ > <0x00000000 0x08340000 0 0x40000>; /* MC control reg */ > msi-parent = <&its>; > + /* define map for ICIDs 23-64 */ > + iommu-map = <23 &smmu 23 41>; > #address-cells = <3>; > #size-cells = <1>; > >