From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752237AbaEaSlW (ORCPT ); Sat, 31 May 2014 14:41:22 -0400 Received: from mout.kundenserver.de ([212.227.17.10]:61210 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751578AbaEaSlU (ORCPT ); Sat, 31 May 2014 14:41:20 -0400 From: Arnd Bergmann To: Liviu Dudau Cc: Bjorn Helgaas , Kumar Gala , Rob Herring , Rob Herring , Grant Likely , 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: Sat, 31 May 2014 20:41:04 +0200 Message-ID: <4756033.LkcFQN0chs@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.11.0-18-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1401496601-31983-2-git-send-email-Liviu.Dudau@arm.com> 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> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V02:K0:m7y/onU88UNiHjaSb5DKUfR5HJ+n0+FWVAeIkb3la3c VS49vrgjYVMlSYIHYs4wqCjHLP2OMTeVoxh2Iom45olYqOXyJA scfrhOF7ZsqtL0zYQ8CfW7xKex9vJUtP4CJ8AKd/sU/gS9fe8p toUQv4MOgedgZPaFx8QQWfl4/WAheIoW+kv2pWJyG5o6RKeAHI Nv9z6HFM33+GwwQLcy3B30ZO9yvYuscSda9N17zSIY4wyevWmQ 2jZXOBoYaOqqNhQFojfjNEUrmilIMha1V0Z47IVFk3Zj8IWMqQ QxUN/UreqhMcZVanjJmbCh0S96Zgfy8BWa5U8wQRYH64SLud25 69eDYqpAd4Bjyo52O7VY= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? Arnd