Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1407157
| From | Bjorn Helgaas <helgaas@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream |
| Date | 2016-05-25 20:40 +0200 |
| Message-ID | <rCLSN-4jE-3@gated-at.bofh.it> (permalink) |
| References | <rCeat-8d9-1@gated-at.bofh.it> <rCKk2-3j5-1@gated-at.bofh.it> <rCKN4-3HL-11@gated-at.bofh.it> <rCLg5-3S1-5@gated-at.bofh.it> <rCLzs-4dm-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, May 25, 2016 at 02:19:01PM -0400, Sinan Kaya wrote: > On 5/25/2016 1:50 PM, Bjorn Helgaas wrote: > >> > You are saying that it is OK to enable L0s on just one side of the > >> > link as long as both sides support L0s. > > I'm not sure what you mean by the link parameters not being > > compatible, but I think it is legal to enable L0s on only one > > direction. > > I'm talking about L0s acceptable and entry latency times used to > determine when L0s can be enabled. Oh, I see. My understanding (again, I'm not a hardware person or a PCIe spec expert) is that the latency numbers are an internal device issue, not a PCIe link issue. From a PCIe point of view, I think we *could* enable L0s even if the device's latency requirements wouldn't be met. The PCIe link itself should work fine, but the device may have internal issues like FIFO overflows. Of course, we want the device to work correctly, so we *shouldn't* enable L0s if it would cause us to exceed the device's latency tolerance. It looks like the code enforces this by clearing bits in link->aspm_capable (effectively pretending L0s or L1 are unsupported) if the latency is too high. Bjorn
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Ocean HY1 He <hehy1@lenovo.com> - 2016-05-24 08:40 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Bjorn Helgaas <helgaas@kernel.org> - 2016-05-24 14:00 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Sinan Kaya <okaya@codeaurora.org> - 2016-05-24 16:50 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Bjorn Helgaas <helgaas@kernel.org> - 2016-05-25 18:40 +0200
RE: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Ocean HY1 He <hehy1@lenovo.com> - 2016-05-25 15:10 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Bjorn Helgaas <helgaas@kernel.org> - 2016-05-25 19:00 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Sinan Kaya <okaya@codeaurora.org> - 2016-05-25 19:30 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Bjorn Helgaas <helgaas@kernel.org> - 2016-05-25 20:00 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Sinan Kaya <okaya@codeaurora.org> - 2016-05-25 20:20 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Bjorn Helgaas <helgaas@kernel.org> - 2016-05-25 20:40 +0200
Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and downstream Sinan Kaya <okaya@codeaurora.org> - 2016-05-25 22:50 +0200
csiph-web