From: Julian Sikorski <belegdol@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>
Cc: "open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>,
linux-acpi@vger.kernel.org, rrangel@chromium.org,
david.e.box@linux.intel.com, Shyam-sundar.S-k@amd.com,
Alexander.Deucher@amd.com, prike.liang@amd.com
Subject: Re: [PATCH v5 2/2] acpi: PM: Add quirks for AMD Renoir/Lucienne CPUs to force the D3 hint
Date: Fri, 4 Jun 2021 21:59:53 +0200 [thread overview]
Message-ID: <efa36cd9-c125-e660-048d-86b7178fbdbd@gmail.com> (raw)
In-Reply-To: <20210604165403.2317-2-mario.limonciello@amd.com>
Am 04.06.21 um 18:54 schrieb Mario Limonciello:
> AMD systems from Renoir and Lucienne require that the NVME controller
> is put into D3 over a Modern Standby / suspend-to-idle
> cycle. This is "typically" accomplished using the `StorageD3Enable`
> property in the _DSD, but this property was introduced after many
> of these systems launched and most OEM systems don't have it in
> their BIOS.
>
> On AMD Renoir without these drives going into D3 over suspend-to-idle
> the resume will fail with the NVME controller being reset and a trace
> like this in the kernel logs:
> ```
> [ 83.556118] nvme nvme0: I/O 161 QID 2 timeout, aborting
> [ 83.556178] nvme nvme0: I/O 162 QID 2 timeout, aborting
> [ 83.556187] nvme nvme0: I/O 163 QID 2 timeout, aborting
> [ 83.556196] nvme nvme0: I/O 164 QID 2 timeout, aborting
> [ 95.332114] nvme nvme0: I/O 25 QID 0 timeout, reset controller
> [ 95.332843] nvme nvme0: Abort status: 0x371
> [ 95.332852] nvme nvme0: Abort status: 0x371
> [ 95.332856] nvme nvme0: Abort status: 0x371
> [ 95.332859] nvme nvme0: Abort status: 0x371
> [ 95.332909] PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -16
> [ 95.332936] nvme 0000:03:00.0: PM: failed to resume async: error -16
> ```
>
> The Microsoft documentation for StorageD3Enable mentioned that Windows has
> a hardcoded allowlist for D3 support, which was used for these platforms.
> Introduce quirks to hardcode them for Linux as well.
>
> As this property is now "standardized", OEM systems using AMD Cezanne and
> newer APU's have adopted this property, and quirks like this should not be
> necessary.
>
> CC: Julian Sikorski <belegdol@gmail.com>
> CC: Shyam-sundar S-k <Shyam-sundar.S-k@amd.com>
> CC: Alexander Deucher <Alexander.Deucher@amd.com>
> CC: Rafael J. Wysocki <rjw@rjwysocki.net>
> CC: Prike Liang <prike.liang@amd.com>
> Link: https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/power-management-for-storage-hardware-devices-intro
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/acpi/device_pm.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> Changes from v4->v5:
> * Add this patch back in as it's been made apparent that the
> system needs to be hardcoded for these.
> Changes:
> - Drop Cezanne - it's now covered by StorageD3Enable
> - Rebase ontop of acpi_storage_d3 outside of NVME
Tested-by: Julian Sikorski <belegdol@gmail.com>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-06-04 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 16:54 [PATCH v5 1/2] acpi: PM: Move check for _DSD StorageD3Enable property to acpi Mario Limonciello
2021-06-04 16:54 ` [PATCH v5 2/2] acpi: PM: Add quirks for AMD Renoir/Lucienne CPUs to force the D3 hint Mario Limonciello
2021-06-04 17:43 ` Raul Rangel
2021-06-04 17:57 ` Limonciello, Mario
2021-06-04 18:48 ` Deucher, Alexander
2021-06-04 19:59 ` Julian Sikorski [this message]
2021-06-07 14:39 ` Rafael J. Wysocki
2021-06-04 17:03 ` [PATCH v5 1/2] acpi: PM: Move check for _DSD StorageD3Enable property to acpi Raul Rangel
2021-06-07 14:36 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=efa36cd9-c125-e660-048d-86b7178fbdbd@gmail.com \
--to=belegdol@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=axboe@fb.com \
--cc=david.e.box@linux.intel.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mario.limonciello@amd.com \
--cc=prike.liang@amd.com \
--cc=rjw@rjwysocki.net \
--cc=rrangel@chromium.org \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox