Hi Sarah, Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> writes: >> > Can you pinpoint the commit that introduced the regression? >> >> f5182b4155b9d686c5540a6822486400e34ddd98 "xhci: Disable MSI for some Fresco Logic hosts." >> >> Technically, this is not per se the commit which introduced the >> regression but the one that *partially* fixed it by introducing the XHCI >> quirk to skip MSI enabling for Fresco Logic chips. The thing is it >> should have included the FL1009 in the targets. Sarah, can you confirm >> this? > > I don't know if it should have included FL1009, it was just a guess, > based on the fact that the 0x1000 and 0x1400 devices did need MSI > disabled. I can attempt to ask the Fresco Logic folks I know, but I'm > not sure if/when I'll get a response back. > > That still doesn't necessarily rule out MSI issues in the Marvell PCI > host controller code. Can you attach another PCI device with MSI > support under the host and see if it works? The various Armada-based devices I have are NAS which do not have PCIe slots to plug additional devices (everything is soldered). I don't know which device Thomas used for its tests. Just in case, I also added Willy in CC: who have various boards and may also have done more test with additional PCIe devices and CONFIG_PCI_MSI enabled on 3.13 kernel. Cheers, a+ -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
