From: Markus Elfring <Markus.Elfring@web.de>
To: Mario Limonciello <mario.limonciello@amd.com>,
linux-pci@vger.kernel.org, linux-usb@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Daniel Drake <drake@endlessos.org>, Gary Li <Gary.Li@amd.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 2/4] PCI: Verify functions currently in D3cold have entered D0
Date: Wed, 19 Jun 2024 20:45:09 +0200 [thread overview]
Message-ID: <053f4c3b-6eb4-43cc-b424-e91c047c90d5@web.de> (raw)
In-Reply-To: <20240613054204.5850-3-mario.limonciello@amd.com>
…
> As PCIe r6.0 sec 5.8 specifies that the device will have gone
> through a conventional reset it may take some time for the
> device to be ready.
>
> Wait up to 1 sec as specified in PCIe r6.0 sec 6.6.1 for a device
> in D3cold to return to D0.
Would you like to add the tag “Fixes” accordingly?
Regards,
Markus
next prev parent reply other threads:[~2024-06-19 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 5:42 [PATCH 0/4] Verify devices transition from D3cold to D0 Mario Limonciello
2024-06-13 5:42 ` [PATCH 1/4] PCI: Check PCI_PM_CTRL in pci_dev_wait() Mario Limonciello
2024-06-19 18:33 ` Markus Elfring
2024-06-19 18:44 ` Mario Limonciello
2024-06-13 5:42 ` [PATCH 2/4] PCI: Verify functions currently in D3cold have entered D0 Mario Limonciello
2024-06-19 18:45 ` Markus Elfring [this message]
2024-06-19 18:46 ` Mario Limonciello
2024-06-13 5:42 ` [PATCH 3/4] PCI: Allow Ryzen XHCI controllers into D3cold and drop delays Mario Limonciello
2024-06-13 5:42 ` [PATCH 4/4] PCI: Drop Radeon quirk for Macbook Pro 8.2 Mario Limonciello
2024-06-18 13:14 ` [PATCH 0/4] Verify devices transition from D3cold to D0 Mika Westerberg
2024-06-18 16:56 ` Mario Limonciello
2024-06-19 5:29 ` Mika Westerberg
2024-06-19 18:50 ` Mario Limonciello
2024-06-25 15:43 ` Mario Limonciello
2024-06-26 7:53 ` Mika Westerberg
2024-07-09 3:07 ` Mario Limonciello
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=053f4c3b-6eb4-43cc-b424-e91c047c90d5@web.de \
--to=markus.elfring@web.de \
--cc=Gary.Li@amd.com \
--cc=bhelgaas@google.com \
--cc=drake@endlessos.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mathias.nyman@intel.com \
--cc=mika.westerberg@linux.intel.com \
/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