From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757211AbaCTM0W (ORCPT ); Thu, 20 Mar 2014 08:26:22 -0400 Received: from moutng.kundenserver.de ([212.227.126.187]:62905 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750960AbaCTM0T (ORCPT ); Thu, 20 Mar 2014 08:26:19 -0400 From: Arnd Bergmann To: Liviu Dudau Subject: Re: [PATCH v7 3/3] arm64: Add architecture support for PCI Date: Thu, 20 Mar 2014 13:26:02 +0100 User-Agent: KMail/1.12.2 (Linux/3.8.0-22-generic; KDE/4.3.2; x86_64; ; ) Cc: Catalin Marinas , "linux-pci" , Bjorn Helgaas , Will Deacon , Benjamin Herrenschmidt , "linaro-kernel" , LKML , "devicetree@vger.kernel.org" , LAKML , Tanmay Inamdar , Grant Likely References: <1394811258-1500-1-git-send-email-Liviu.Dudau@arm.com> <201403201217.22339.arnd@arndb.de> <20140320113820.GH6457@e106497-lin.cambridge.arm.com> In-Reply-To: <20140320113820.GH6457@e106497-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201403201326.02377.arnd@arndb.de> X-Provags-ID: V02:K0:/pp3LGRdLYynWswgyKTqFM6wLapSFEgUrjU2AsCl3WA kj7WooWshYABaa1osaZBwH6nt+a4HAsxgNJLG3+NQgHyfKnqtH fVhrit593CSEPRSqPFdhcGUs/9qKS+U2zkndCl2HgP5JmS4KOF tYPze33USJNA0UzxsULlnzAVIu3BpTcA0J9e+nl9LN58dYx7cH YiP7Ks0+3i9QOaMmmhicDo6UeuQF3jxz20daso7DDEsxsIB/s4 aQn6OfXnRQY/wmrN+Xgm1sTgYV9fFzi6Ezbyci9gDqWebC0v9u hCd2zS8T9NHo3TR6q3yNU5+cmBibrpDN01o76jxnIBRf5p/zZm oh3//buPKRL+LoWx0txV4cglJeRBff8W0Hge7q5hd Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 20 March 2014, Liviu Dudau wrote: > > I don't even understand why you want to create a generic pci_address_to_pio > > implementation, when we don't need that for arm64 at all. Unless I'm > > missing something important, that function is only called in case of > > PCI_PROBE_DEVTREE with pci_of_scan on PowerPC. I don't expect any > > architecture to do the same thing, and the only other architecture that > > needs something like it (sparc) has a different implementation. > > Because in my [v7 2/6]* patch for the generic host bridge support I start > using pci_address_to_pio to fix the conversion of PCI ranges to resources. > That requires an arm64 (or more correctly, an arch with memory mapped IO > specific) version of pci_address_to_pio(). Yes, but why do you use it there? Arnd