lkml.org 
[lkml]   [2022]   [Apr]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [V3] PCI: fu740: Drop to 2.5GT/s to fix initial device probing on some boards
On Wed, 23 Mar 2022, Ben Dooks wrote:

> > FWIW, I have tested this and it solved my issue with nvme not being probed,
> > so:
> >
> > Tested-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
>
> Ok, great. Our test rig seems to be still working with this.

I ran simple verification of your change by interrupting U-Boot after a
power-up and issuing:

=> setenv boot_pci_enum true

at the command prompt before booting from the uSD card and curiously
enough the root port comes up with the Link Capabilities Register
reporting the lack of Link Bandwidth Notification Capability in this
scenario, while it reports its presence if booted undisturbed, i.e.:

LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <4us, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp+

vs:

LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <4us, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+

It is fully reproducible.

Any idea what might be causing it? I can't see it being explicitly set
or cleared anywhere, be it in U-Boot or Linux, so it must be done by the
device itself depending on something. And the lack of this capability
seems to me like non-compliance for a multiple-lane, multiple-speed
device.

Maciej

\
 
 \ /
  Last update: 2022-04-14 02:11    [W:0.087 / U:0.252 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site