Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755440AbaFBPJy (ORCPT ); Mon, 2 Jun 2014 11:09:54 -0400 Received: from mail-we0-f173.google.com ([74.125.82.173]:56002 "EHLO mail-we0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752339AbaFBPJu (ORCPT ); Mon, 2 Jun 2014 11:09:50 -0400 From: Grant Likely Subject: Re: [PATCH 1/2] pci: Add IORESOURCE_BIT entry for PCIe ECAM resources. To: Arnd Bergmann , Liviu Dudau Cc: Bjorn Helgaas , Kumar Gala , 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 In-Reply-To: <4756033.LkcFQN0chs@wuerfel> References: <20140530233034.GH1677@bart.dudau.co.uk> <1401496601-31983-1-git-send-email-Liviu.Dudau@arm.com> <1401496601-31983-2-git-send-email-Liviu.Dudau@arm.com> <4756033.LkcFQN0chs@wuerfel> Date: Mon, 02 Jun 2014 16:09:45 +0100 Message-Id: <20140602150945.964D4C40381@trevor.secretlab.ca> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 31 May 2014 20:41:04 +0200, Arnd Bergmann wrote: > On Saturday 31 May 2014 01:36:40 Liviu Dudau wrote: > > We would like to be able to describe PCIe ECAM resources as > > IORESOURCE_MEM blocks while distinguish them from standard > > memory resources. Add an IORESOURCE_BIT entry for this case. > > > > Signed-off-by: Liviu Dudau > > I still don't see any value in this at all. What is the advantage > of doing this opposed to just having a standardized 'reg' property > for a particular compatible string? I'm inclined to agree. It doesn't seem appropriate to put config space in ranges, and the host controller binding is responsible for identifying how config space is memory mapped. g. -- 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/