From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.17.13]:52120 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751338AbaFBTQJ convert rfc822-to-8bit (ORCPT ); Mon, 2 Jun 2014 15:16:09 -0400 From: Arnd Bergmann To: Kumar Gala Cc: Grant Likely , Liviu Dudau , Bjorn Helgaas , Rob Herring , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-pci@vger.kernel.org" , linux-arm-msm , "linux-arm-kernel@lists.infradead.org" , Kishon Vijay Abraham I Subject: Re: [PATCH 1/2] pci: Add IORESOURCE_BIT entry for PCIe ECAM resources. Date: Mon, 02 Jun 2014 21:15:46 +0200 Message-ID: <4495090.ktpdXEyibD@wuerfel> In-Reply-To: <2F6515B1-48FE-4ED6-908E-CC1CAD7AF403@codeaurora.org> References: <20140530233034.GH1677@bart.dudau.co.uk> <20140602162306.4AB0FC40476@trevor.secretlab.ca> <2F6515B1-48FE-4ED6-908E-CC1CAD7AF403@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Sender: linux-pci-owner@vger.kernel.org List-ID: On Monday 02 June 2014 13:09:08 Kumar Gala wrote: > > However, what do we do with the 2 cases that exist in upstream that > >> are using ranges for cfg space? > > > > Ignore them in the core code? Make the specific host controller handle > > them I would think. > > I just meant, should we ‘break’ their DTs and move them from using ranges to reg? dw-pcie is used on a lot of systems, I think we should make the common part of that driver always handle config space in a common way, and move out the part that parses the ranges property into the individual soc-specific glue drivers that want to keep optional backwards compatibility with existing dtbs. Which one is the other driver? Arnd