On Wed, 2009-04-08 at 15:53 -0500, Kumar Gala wrote: > I was wondering if we have anything that tracks regions associated > with the "inbound" side of a pci_bus. > > What I mean is on embedded PPC we have window/mapping registers for > both inbound (accessing memory on the SoC) and outbound (access PCI > device MMIO, IO etc). The combination of the inbound & outbound > convey what exists in the PCI address space vs CPU physical address > space (and how to map from one to the other). Today in the PPC land > we only attach outbound windows to the pci_bus. So technically the > inbound side information (like what subset of physical memory is > visible on the PCI bus) seems to be lost. On powerpc, we do keep track of the offset, but that's about it. Tracking inbound ranges is very platform specific though. You can have multiple inbound windows with different translations, in some cases some via iommu and some not, or windows aliasing the same target memory but with different attributes, etc... I don't think there's that much interest in trying to create generic code to keep track. Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
