Displaying 5 results from an estimated 5 matches for "pcie_wait_for_link_delay".
2019 Dec 20
1
Tracking down severe regression in 5.3-rc4/5.4 for TU116 - assistance needed
...ems to be
Revert "PCI: Add missing link delays required by the PCIe spec"
Can you try v5.5-rcX without any additional changes? It should include
the same fix done bit differently (trying to avoid breaking systems
which caused us to revert the previous one):
4827d63891b6 PCI/PM: Add pcie_wait_for_link_delay()
ad9001f2f411 PCI/PM: Add missing link delays required by the PCIe spec
2019 Nov 20
0
[PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges
...eep(delay);
> } else {
> - pci_dbg(dev, "waiting %d ms for downstream link, after activation\n",
> + pci_info(dev, "waiting %d ms for downstream link, after activation\n",
> delay);
> if (!pcie_wait_for_link_delay(dev, true, delay)) {
> /* Did not train, no need to wait any further */
> @@ -4753,7 +4748,7 @@ void pci_bridge_wait_for_secondary_bus(struct pci_dev *dev)
> }
>
> if (!pci_device_is_present(child)) {
> - pci_dbg(child, "w...
2019 Nov 20
1
[PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges
..., delay);
+ pci_info(dev, "waiting %d ms for downstream link\n", delay);
msleep(delay);
} else {
- pci_dbg(dev, "waiting %d ms for downstream link, after activation\n",
+ pci_info(dev, "waiting %d ms for downstream link, after activation\n",
delay);
if (!pcie_wait_for_link_delay(dev, true, delay)) {
/* Did not train, no need to wait any further */
@@ -4753,7 +4748,7 @@ void pci_bridge_wait_for_secondary_bus(struct pci_dev *dev)
}
if (!pci_device_is_present(child)) {
- pci_dbg(child, "waiting additional %d ms to become accessible\n", delay);
+ pci_info...
2019 Nov 20
4
[PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges
On Wed, Nov 20, 2019 at 04:37:14PM +0100, Karol Herbst wrote:
> On Wed, Nov 20, 2019 at 4:15 PM Mika Westerberg
> <mika.westerberg at intel.com> wrote:
> >
> > On Wed, Nov 20, 2019 at 01:11:52PM +0100, Karol Herbst wrote:
> > > On Wed, Nov 20, 2019 at 1:09 PM Mika Westerberg
> > > <mika.westerberg at intel.com> wrote:
> > > >
> >
2019 Dec 19
3
Tracking down severe regression in 5.3-rc4/5.4 for TU116 - assistance needed
On 2019-12-16 19:45, Ilia Mirkin wrote:
> The obvious candidate based on a quick scan is
> 0acf5676dc0ffe0683543a20d5ecbd112af5b8ee -- it merges a fix that
> messes with PCI stuff, and there lie dragons. You could try building
> that commit, and if things still work, then I have no idea (and you've
Nice shot Ilia!
I managed to build kernel from suspected bd112af5b8ee and it fails