On Sat, 31 May 2014 20:41:04 +0200, Arnd Bergmann <a...@arndb.de> 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 <liviu.du...@arm.com> > > 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
