Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754968AbaGDJGQ (ORCPT ); Fri, 4 Jul 2014 05:06:16 -0400 Received: from mout.kundenserver.de ([212.227.17.24]:62014 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753236AbaGDJGM (ORCPT ); Fri, 4 Jul 2014 05:06:12 -0400 From: Arnd Bergmann To: Varun Sethi Cc: Thierry Reding , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Stephen Warren , Will Deacon , Joerg Roedel , Olav Haugan , "devicetree@vger.kernel.org" , Grant Grundler , Rhyland Klein , "iommu@lists.linux-foundation.org" , "linux-kernel@vger.kernel.org" , Marc Zyngier , Allen Martin , Paul Walmsley , "linux-tegra@vger.kernel.org" , Cho KyongHo , Dave Martin , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH v3 02/10] devicetree: Add generic IOMMU device tree bindings Date: Fri, 04 Jul 2014 11:05:01 +0200 Message-ID: <9506037.pCJq3zRKJU@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.11.0-18-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <9ffe3c3871ef4b60a955259bfa0bed6c@BL2PR03MB468.namprd03.prod.outlook.com> References: <1403815790-8548-1-git-send-email-thierry.reding@gmail.com> <1403815790-8548-3-git-send-email-thierry.reding@gmail.com> <9ffe3c3871ef4b60a955259bfa0bed6c@BL2PR03MB468.namprd03.prod.outlook.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V02:K0:8CR1kfRuDyEchq7L2uySjSXYC1grhwK0E7PuqekAvHR Q44tW0Ym6+ng2GqMWKjCKz63rNFHQKMOg04qCCKJcXwovrL//7 8bd6KdO8mnBx0mrP6nAhimpS/KP8oGJA2OkRpT2XNEYPXXZozs qNL2Jh+J+Av2TQLccLoDjFe1lsiSNBArEi3VrVq5GNe5M1/8LU F9ARfeiJkD2bL7UjflwAixH0WC7idXFClqOvxJ6VITg/D2En/d L08rP7SimRPhpiTKOE7b904S52H37wbAGi6bGEAJurpli/J01O Lc6DgabV5+lZZFSRHAy/gT00GC1SQW69eqgFBzJMxffy5/vYMd m5UUlH3+s+JO2IDgxpw4= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 04 July 2014 06:42:48 Varun Sethi wrote: > Master node corresponds to the device node, right? Master ID would correspond > to Stream ID? We are already using "iommu-parent" property to link a device > to its corresponding IOMMU. We can use the same property instead of using "iommus". I don't see "iommu-parent" used anywhere, just "fsl,iommu-parent". We can probably allow "fsl,iommu-parent" as an alias for "iommus" for backwards- compatibility if that helps you on PowerPC. For ARM, I'd prefer to mandate that we use just "iommus". Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/