@ Brad please see response from Intel on your follow up on questions:

 (a) affect Nvidia's use of DPC / EDR, depending upon how their firmware is 
negotiating the control with the operating system, and 
Response: As per spec, platforms should rely on _OSC to negotiate PCIe 
capabilities ownership. So for new platforms NVDIA should start using_OSC 
instead of HEST table.

(b) affect our existing installed base platforms that currently end up 
negotiating one way, but end up with a different result under this patch.  
E.g., the platform advertises "firmware first" in the ACPI  HEST, but not via 
_OSC.  I think it is more likely that server class  systems will already do 
this correctly, and that embedded / "IoT" type devices are more likely to see 
an impact from this change.
Response: For existing platforms, since they don't align with spec, 
recommendation is using pci quirks to create exception for their use cases.

This is platform generic enhancement and can be tested on Intel

There was a question also on Diagnostics:
EDR related error messages:
1. "Failed to install notify handler"
2. "Firmware failed to locate DPC port" (Issue with 0x0D _DSM)
3. "This device doesn't support DPC"
4. "Invalid DPC trigger"

EDR success messages:
1. "EDR event received" ( for receiving successful EDR event)
2. "device recovery successful" ( for successful recovery)

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  [Intel] Add Error Disconnect Recover support

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to