On Fri, Apr 16, 2021 at 02:54:34PM +0800, Prike Liang wrote:
In the NVMe controller default suspend-resume seems only save/restore the NVMe link state by APST opt and the NVMe remains in D0 during this time. Then the NVMe device will be shutdown by SMU firmware in the s2idle entry and then will lost the NVMe power context during s2idle resume.Finally, the NVMe command queue request will be processed abnormally and result in access timeout.This issue can be settled by using PCIe power set with simple suspend-resume process path instead of APST get/set opt.
In this patch prepare a PCIe RC bus flag to identify the platform whether need the quirk.
Cc: stable@vger.kernel.org # 5.11+ Signed-off-by: Prike Liang Prike.Liang@amd.com Signed-off-by: Shyam Sundar S K Shyam-sundar.S-k@amd.com [ck: split patches for nvme and pcie] Signed-off-by: Chaitanya Kulkarni chaitanya.kulkarni@wdc.com Signed-off-by: Keith Busch kbusch@kernel.org
Just a "Suggested-by:" from me is fine. I'm glad you were able to confirm this is successful, so I can add my Ack as well
Acked-by: Keith Busch kbusch@kernel.org