On Thu, Feb 10, 2022 at 06:56:35AM -0800, Keith Busch wrote:This is all you needed to say
Apparently it works fine when you disable VMD, so sounds like the
acpi_storage_d3 is set, but we fail to find the correct acpi companion
device when it's in a VMD domain.
I guess the acpi_storage_d3 is set on the VMD device and we need
to propagate that down the entire bus hanging off it.
Is this relevant or necessary?
Which kinda makes sense in the twisted world where vmd was invented,
given that vmd is Intel's evil plot so that only their Windows driver
can bind to these devices,
the vmd device.
Nirmal and Jonathan, can you help to sort this mess out?