On Tue, Jan 17, 2017 at 03:25:49PM +0000, Russell King - ARM Linux wrote: > On Tue, Jan 17, 2017 at 09:14:44AM -0600, Bjorn Helgaas wrote: > > On Wed, Jan 11, 2017 at 08:49:46PM +0100, Uwe Kleine-König wrote: > > > Hello, > > > > > > on an Marvell Armada 385 based machine (Turris Omnia) with 4.9 the > > > ath10k driver fails to bind to the matching hardware if CONFIG_PCIEASPM > > > is enabled: > > > > > > # dmesg | grep ath > > > [ 7.207770] ath10k_pci 0000:02:00.0: Refused to change power state, currently in D3 > > > [ 7.237955] ath10k_pci 0000:02:00.0: failed to wake up device : -110 > > > [ 7.238146] ath10k_pci: probe of 0000:02:00.0 failed with error -110 > > > > > > if however PCIEASPM is off, the driver probes correctly and the ath10k > > > adapter works fine. > > > > > > I wonder if someone has an idea what needs to be done to fix this > > > problem. (OK, I could disable PCIEASPM, but I'd like to have a solution > > > for a distribution kernel where I think PCIEASPM=y is sensible in > > > general.) > > > > Can somebody confirm that this system (Marvell Armada 385-based Turris > > Omnia) does actually support ASPM in hardware? > > What sort of "hardware" are you referring to? > > From my reading of the specs, ASPM doesn't require any external hardware. > It's all done inside the PCIe root hub and PCIe device. Right. My question is just whether we know that the Marvell PCIe root hub hardware works correctly with respect to ASPM. The PCI core isn't doing anything special for Marvell, so problems here are likely to be either in the Marvell hardware or in the pci-mvebu.c driver. > The PCIe spec specifically prohibits cutting power supplies and clocks to > PCIe devices during L0s and L1, with the exception that the PCIe clock may > be stopped in L1 if CLKREQ# is deasserted. CLKREQ# handling generally > requires GPIO usage, and as there's no support for that, there's no support > for stopping the PCIe clock in L1. We do the correct thing there, > preventing the PCI_EXP_LNKCTL_CLKREQ_EN bit being set. > > That all said, it would probably be a good idea to throw some printk() > debugging into mvebu_sw_pci_bridge_write() and mvebu_sw_pci_bridge_read() > so we can see what's going on at that level, and maybe also some debug > in mvebu_pcie_hw_wr_conf() and mvebu_pcie_hw_rd_conf() so we can see > what's happening at the PCIe device too. Uwe has already done that; the dmesg logs including this instrumentation are at https://bugzilla.kernel.org/show_bug.cgi?id=192441 -- 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
