On Monday 19 January 2015 10:40:39 Rob Herring wrote: > > I don't really like exposing ranges to host drivers. We've worked to > not do that. So perhaps we need to rethink the API. I think we need to > provide each range as a pair of resources which are the CPU address > and PCI address. Perhaps an iterator is kind of pointless here. We do > different things for each one. Are there cases with more than a single > i/o space, non-prefetch memory and prefetch memory range? Perhaps we > should just get the i/o and memory resources as separate calls. Just > tossing out some ideas here. Nice idea, that could be similar to platform_get_resource(). We probably also need the distinction between CPU address and (parent) bus address here. In most drivers they are the same, but we actually need to program the latter one into the PCI host bridge registers. Arnd -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
