Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753718AbbBYUqA (ORCPT ); Wed, 25 Feb 2015 15:46:00 -0500 Received: from arroyo.ext.ti.com ([192.94.94.40]:54807 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753686AbbBYUp5 (ORCPT ); Wed, 25 Feb 2015 15:45:57 -0500 Message-ID: <54EE344D.5060403@ti.com> Date: Wed, 25 Feb 2015 15:45:01 -0500 From: Murali Karicheri User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Arnd Bergmann CC: Bjorn Helgaas , , , , , , Joerg Roedel , Grant Likely , Rob Herring , Will Deacon , Russell King , Suravee Suthikulpanit Subject: Re: [PATCH v6 6/7] PCI: update dma configuration from DT References: <1423173179-10227-1-git-send-email-m-karicheri2@ti.com> <20150225015317.GO6220@google.com> <54EDF236.40101@ti.com> <4781283.CC9oFpsHLJ@wuerfel> In-Reply-To: <4781283.CC9oFpsHLJ@wuerfel> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2061 Lines: 48 On 02/25/2015 11:09 AM, Arnd Bergmann wrote: > On Wednesday 25 February 2015 11:03:02 Murali Karicheri wrote: >> >>> (I don't know exactly how these patches all fit together, so that's >>> probably not accurate, but that's the *sort* of thing I'd like to include.) >>> >>> If that actually *is* what's going on, I have to wonder why this isn't >>> implemented as a very simple IOMMU instead of adding dma_pfn_offset, >>> which is present on all arches but only used on ARM. In some sense that >>> offset is parallel but incompatible with an IOMMU: they both translate DMA >>> addresses into system RAM addresses. >> >> I don't have much history on any previous discussion on the subject you >> are referring to. I assume it would have happened when >> of_dma_configure() was first introduced. On Keystone, we don't have >> IOMMU support and dma_pfn_offset is needed to translate DMA address to >> System RAM address and vice-versa. So this has to be supported for >> Keystone. There can be enhancement for IOMMU with out impacting this >> feature for Keystone. > > The direction we are taking with IOMMU in general is opposite to what Bjorn > is suggesting: I believe what he wants to say is that we should use the > traditional approach of having a specialized dma_map_ops implementation > for this, just like we do for IOMMU implementations on x86, IA64 or PowerPC. > > However, with the recent explosion of IOMMU implementations on ARM, we > are moving towards having a single dma_map_ops structure for all of them, > and that structure does not work with the keystone hardware. Instead, > the normal ARM dma_map_ops have been changed to handle the offset, > which is the same thing we do on PowerPC. > Arnd, Thanks for the clarification. Murali > Arnd -- Murali Karicheri Linux Kernel, Texas Instruments -- 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/