On Thu, Nov 24, 2011 at 7:18 AM, Tejun Heo <tj@xxxxxxxxxx> wrote: > Hello, > > On Wed, Nov 23, 2011 at 2:47 PM, Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> wrote: >>> Weird, that basically means that somehow pci_iomap() isn't >>> synchronous. ie. you need to way some time after pci_iomap() before >>> being able to access the mapped address. Seems like arch / pci >>> weirdness. Jesse, Russell, any ideas? >> >> As Russel said, pci_iomap shouldn't be async. But maybe something else >> in the init function is doing a chip reset or causing the chip to go >> off into the weeds for a short time? That's generally the cause of >> target timeouts for PCI devices. > > Yeah, that's much more plausible. Weird that it doesn't happen on x86 > tho. Maybe different timeouts? Pratyush, can you look at bus trace and > see what's going on? It also does not happen always with ARM too. As said earlier only when I run the system at increased CPU frequency. Do you suggest to trace PCIe bus using PCIe bus analyser. I can arange analyser to do that. But I do not see any kind of abort (like PCIe host/target abort) in this case. So will it really help? Is it possible to share datasheet of SIL3531? Regards Pratyush > > Thanks. > > -- > tejun > -- 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
