* Query related to shutting down NVMe during system suspend @ 2022-02-01 16:22 Vidya Sagar 2022-02-01 16:30 ` Keith Busch 2022-02-09 20:26 ` Keith Busch 0 siblings, 2 replies; 14+ messages in thread From: Vidya Sagar @ 2022-02-01 16:22 UTC (permalink / raw) To: rafael.j.wysocki, keith.busch, hch Cc: bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel Hi Rafael & Christoph, My query is regarding the comment and the code that follows after it at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 What I understood from it is that, there is an underlying assumption that the power to the devices is not removed during the suspend call. In the case of device-tree based platforms like Tegra194, power is indeed removed to the devices during suspend-resume process. Hence, the NVMe devices need to be taken through the shutdown path irrespective of whether the ASPM states are enabled or not. I would like to hear from you the best method to follow to achieve this. Thanks & Regards, Vidya Sagar ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-01 16:22 Query related to shutting down NVMe during system suspend Vidya Sagar @ 2022-02-01 16:30 ` Keith Busch 2022-02-01 16:58 ` Vidya Sagar 2022-02-01 17:17 ` Rafael J. Wysocki 2022-02-09 20:26 ` Keith Busch 1 sibling, 2 replies; 14+ messages in thread From: Keith Busch @ 2022-02-01 16:30 UTC (permalink / raw) To: Vidya Sagar Cc: rafael.j.wysocki, keith.busch, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: > Hi Rafael & Christoph, > My query is regarding the comment and the code that follows after it at > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 > What I understood from it is that, there is an underlying assumption > that the power to the devices is not removed during the suspend call. > In the case of device-tree based platforms like Tegra194, power is > indeed removed to the devices during suspend-resume process. Hence, the > NVMe devices need to be taken through the shutdown path irrespective of > whether the ASPM states are enabled or not. > I would like to hear from you the best method to follow to achieve this. Since platform makers can't converge on how to let a driver know what it's supposed to do, I suggest we default to the simple shutdown suspend all the time. We can add a module parameter to let a user request nvme power management if they really want it. No matter what we do here, someone is going to complain, but at least simple shutdown is safe... ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-01 16:30 ` Keith Busch @ 2022-02-01 16:58 ` Vidya Sagar 2022-02-07 10:57 ` nitirawa 2022-02-01 17:17 ` Rafael J. Wysocki 1 sibling, 1 reply; 14+ messages in thread From: Vidya Sagar @ 2022-02-01 16:58 UTC (permalink / raw) To: Keith Busch Cc: rafael.j.wysocki, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel Thanks for the super quick reply and I couldn't agree more. On 2/1/2022 10:00 PM, Keith Busch wrote: > External email: Use caution opening links or attachments > > > On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: >> Hi Rafael & Christoph, >> My query is regarding the comment and the code that follows after it at >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 >> What I understood from it is that, there is an underlying assumption >> that the power to the devices is not removed during the suspend call. >> In the case of device-tree based platforms like Tegra194, power is >> indeed removed to the devices during suspend-resume process. Hence, the >> NVMe devices need to be taken through the shutdown path irrespective of >> whether the ASPM states are enabled or not. >> I would like to hear from you the best method to follow to achieve this. > > Since platform makers can't converge on how to let a driver know what > it's supposed to do, I suggest we default to the simple shutdown suspend > all the time. We can add a module parameter to let a user request nvme > power management if they really want it. No matter what we do here, > someone is going to complain, but at least simple shutdown is safe... > ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-01 16:58 ` Vidya Sagar @ 2022-02-07 10:57 ` nitirawa 2022-02-07 12:11 ` Vidya Sagar 0 siblings, 1 reply; 14+ messages in thread From: nitirawa @ 2022-02-07 10:57 UTC (permalink / raw) To: Vidya Sagar Cc: Keith Busch, rafael.j.wysocki, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On 2022-02-01 22:28, Vidya Sagar wrote: > Thanks for the super quick reply and I couldn't agree more. > > On 2/1/2022 10:00 PM, Keith Busch wrote: >> External email: Use caution opening links or attachments >> >> >> On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: >>> Hi Rafael & Christoph, >>> My query is regarding the comment and the code that follows after it >>> at >>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 >>> What I understood from it is that, there is an underlying assumption >>> that the power to the devices is not removed during the suspend call. >>> In the case of device-tree based platforms like Tegra194, power is >>> indeed removed to the devices during suspend-resume process. Hence, >>> the >>> NVMe devices need to be taken through the shutdown path irrespective >>> of >>> whether the ASPM states are enabled or not. >>> I would like to hear from you the best method to follow to achieve >>> this. >> >> Since platform makers can't converge on how to let a driver know what >> it's supposed to do, I suggest we default to the simple shutdown >> suspend >> all the time. We can add a module parameter to let a user request nvme >> power management if they really want it. No matter what we do here, >> someone is going to complain, but at least simple shutdown is safe... >> Hi Vidya, Are you planning to add module parameter based on above discussion. I see similar behaviour even with qualcomm platform. [ 119.994092] nvme nvme0: I/O 9 QID 0 timeout, reset controller [ 120.006612] PM: dpm_run_callback(): pci_pm_resume+0x0/0xe4 returns -16 [ 120.013502] nvme 0001:01:00.0: PM: pci_pm_resume+0x0/0xe4 returned -16 after 60059958 usecs [ 120.022239] nvme 0001:01:00.0: PM: failed to resume async: error -16 Regards, Nitin ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-07 10:57 ` nitirawa @ 2022-02-07 12:11 ` Vidya Sagar 2022-02-07 15:44 ` nitirawa 0 siblings, 1 reply; 14+ messages in thread From: Vidya Sagar @ 2022-02-07 12:11 UTC (permalink / raw) To: nitirawa Cc: Keith Busch, rafael.j.wysocki, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On 2/7/2022 4:27 PM, nitirawa@codeaurora.org wrote: > External email: Use caution opening links or attachments > > > On 2022-02-01 22:28, Vidya Sagar wrote: >> Thanks for the super quick reply and I couldn't agree more. >> >> On 2/1/2022 10:00 PM, Keith Busch wrote: >>> External email: Use caution opening links or attachments >>> >>> >>> On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: >>>> Hi Rafael & Christoph, >>>> My query is regarding the comment and the code that follows after it >>>> at >>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 >>>> >>>> What I understood from it is that, there is an underlying assumption >>>> that the power to the devices is not removed during the suspend call. >>>> In the case of device-tree based platforms like Tegra194, power is >>>> indeed removed to the devices during suspend-resume process. Hence, >>>> the >>>> NVMe devices need to be taken through the shutdown path irrespective >>>> of >>>> whether the ASPM states are enabled or not. >>>> I would like to hear from you the best method to follow to achieve >>>> this. >>> >>> Since platform makers can't converge on how to let a driver know what >>> it's supposed to do, I suggest we default to the simple shutdown >>> suspend >>> all the time. We can add a module parameter to let a user request nvme >>> power management if they really want it. No matter what we do here, >>> someone is going to complain, but at least simple shutdown is safe... >>> > > Hi Vidya, > > Are you planning to add module parameter based on above discussion. I > see similar behaviour even with qualcomm platform. > > [ 119.994092] nvme nvme0: I/O 9 QID 0 timeout, reset controller > [ 120.006612] PM: dpm_run_callback(): pci_pm_resume+0x0/0xe4 returns > -16 > [ 120.013502] nvme 0001:01:00.0: PM: pci_pm_resume+0x0/0xe4 returned > -16 after 60059958 usecs > [ 120.022239] nvme 0001:01:00.0: PM: failed to resume async: error -16 Not really. Keith Busch has already pushed a patch to fix it in a different way and issue is resolved (on Tegra platforms) with that patch. https://lore.kernel.org/all/20220201165006.3074615-1-kbusch@kernel.org/ is that patch. Thanks & Regards, Vidya Sagar > > Regards, > Nitin > > ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-07 12:11 ` Vidya Sagar @ 2022-02-07 15:44 ` nitirawa 2022-02-07 15:47 ` Keith Busch 0 siblings, 1 reply; 14+ messages in thread From: nitirawa @ 2022-02-07 15:44 UTC (permalink / raw) To: Vidya Sagar, Keith Busch Cc: Keith Busch, rafael.j.wysocki, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On 2022-02-07 17:41, Vidya Sagar wrote: > On 2/7/2022 4:27 PM, nitirawa@codeaurora.org wrote: >> External email: Use caution opening links or attachments >> >> >> On 2022-02-01 22:28, Vidya Sagar wrote: >>> Thanks for the super quick reply and I couldn't agree more. >>> >>> On 2/1/2022 10:00 PM, Keith Busch wrote: >>>> External email: Use caution opening links or attachments >>>> >>>> >>>> On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: >>>>> Hi Rafael & Christoph, >>>>> My query is regarding the comment and the code that follows after >>>>> it >>>>> at >>>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 >>>>> What I understood from it is that, there is an underlying >>>>> assumption >>>>> that the power to the devices is not removed during the suspend >>>>> call. >>>>> In the case of device-tree based platforms like Tegra194, power is >>>>> indeed removed to the devices during suspend-resume process. Hence, >>>>> the >>>>> NVMe devices need to be taken through the shutdown path >>>>> irrespective >>>>> of >>>>> whether the ASPM states are enabled or not. >>>>> I would like to hear from you the best method to follow to achieve >>>>> this. >>>> >>>> Since platform makers can't converge on how to let a driver know >>>> what >>>> it's supposed to do, I suggest we default to the simple shutdown >>>> suspend >>>> all the time. We can add a module parameter to let a user request >>>> nvme >>>> power management if they really want it. No matter what we do here, >>>> someone is going to complain, but at least simple shutdown is >>>> safe... >>>> >> >> Hi Vidya, >> >> Are you planning to add module parameter based on above discussion. I >> see similar behaviour even with qualcomm platform. >> >> [ 119.994092] nvme nvme0: I/O 9 QID 0 timeout, reset controller >> [ 120.006612] PM: dpm_run_callback(): pci_pm_resume+0x0/0xe4 returns >> -16 >> [ 120.013502] nvme 0001:01:00.0: PM: pci_pm_resume+0x0/0xe4 returned >> -16 after 60059958 usecs >> [ 120.022239] nvme 0001:01:00.0: PM: failed to resume async: error >> -16 > Not really. > Keith Busch has already pushed a patch to fix it in a different way > and issue is resolved (on Tegra platforms) with that patch. > https://lore.kernel.org/all/20220201165006.3074615-1-kbusch@kernel.org/ > is that patch. > > Thanks & Regards, > Vidya Sagar >> >> Regards, >> Nitin >> >> Thanks Vidya for pointing out the patch . This patch worked for us as well. @keith - Please can we get this merged . Regards, Nitin ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-07 15:44 ` nitirawa @ 2022-02-07 15:47 ` Keith Busch 0 siblings, 0 replies; 14+ messages in thread From: Keith Busch @ 2022-02-07 15:47 UTC (permalink / raw) To: nitirawa Cc: Vidya Sagar, rafael.j.wysocki, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On Mon, Feb 07, 2022 at 09:14:49PM +0530, nitirawa@codeaurora.org wrote: > Thanks Vidya for pointing out the patch . This patch worked for us as well. > @keith - Please can we get this merged . I'm working on it, but I don't think the proposed patch was acceptable. I'm going to look at another option today. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-01 16:30 ` Keith Busch 2022-02-01 16:58 ` Vidya Sagar @ 2022-02-01 17:17 ` Rafael J. Wysocki 1 sibling, 0 replies; 14+ messages in thread From: Rafael J. Wysocki @ 2022-02-01 17:17 UTC (permalink / raw) To: Vidya Sagar, Keith Busch Cc: rafael.j.wysocki, keith.busch, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On Tuesday, February 1, 2022 5:30:54 PM CET Keith Busch wrote: > On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: > > Hi Rafael & Christoph, > > My query is regarding the comment and the code that follows after it at > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 > > What I understood from it is that, there is an underlying assumption > > that the power to the devices is not removed during the suspend call. > > In the case of device-tree based platforms like Tegra194, power is > > indeed removed to the devices during suspend-resume process. Hence, the > > NVMe devices need to be taken through the shutdown path irrespective of > > whether the ASPM states are enabled or not. > > I would like to hear from you the best method to follow to achieve this. > > Since platform makers can't converge on how to let a driver know what > it's supposed to do, I suggest we default to the simple shutdown suspend > all the time. We can add a module parameter to let a user request nvme > power management if they really want it. No matter what we do here, > someone is going to complain, but at least simple shutdown is safe... Agreed. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-01 16:22 Query related to shutting down NVMe during system suspend Vidya Sagar 2022-02-01 16:30 ` Keith Busch @ 2022-02-09 20:26 ` Keith Busch 2022-02-09 21:17 ` nitirawa 2022-02-10 4:11 ` Vidya Sagar 1 sibling, 2 replies; 14+ messages in thread From: Keith Busch @ 2022-02-09 20:26 UTC (permalink / raw) To: Vidya Sagar Cc: rafael.j.wysocki, keith.busch, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: > Hi Rafael & Christoph, > My query is regarding the comment and the code that follows after it at > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 > What I understood from it is that, there is an underlying assumption > that the power to the devices is not removed during the suspend call. > In the case of device-tree based platforms like Tegra194, power is > indeed removed to the devices during suspend-resume process. Hence, the > NVMe devices need to be taken through the shutdown path irrespective of > whether the ASPM states are enabled or not. > I would like to hear from you the best method to follow to achieve this. Christoph prefers to append quirks for platforms that need full device shutdown on s2idle instead of changing the driver default. We use dmi matching for our current platform quirk list. I do not know what the equivalent is for device-tree based platforms. Do you know? ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-09 20:26 ` Keith Busch @ 2022-02-09 21:17 ` nitirawa 2022-02-09 21:47 ` Keith Busch 2022-02-10 4:11 ` Vidya Sagar 1 sibling, 1 reply; 14+ messages in thread From: nitirawa @ 2022-02-09 21:17 UTC (permalink / raw) To: Keith Busch Cc: Vidya Sagar, rafael.j.wysocki, keith.busch, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On 2022-02-10 01:56, Keith Busch wrote: > On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: >> Hi Rafael & Christoph, >> My query is regarding the comment and the code that follows after it >> at >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 >> What I understood from it is that, there is an underlying assumption >> that the power to the devices is not removed during the suspend call. >> In the case of device-tree based platforms like Tegra194, power is >> indeed removed to the devices during suspend-resume process. Hence, >> the >> NVMe devices need to be taken through the shutdown path irrespective >> of >> whether the ASPM states are enabled or not. >> I would like to hear from you the best method to follow to achieve >> this. > > Christoph prefers to append quirks for platforms that need full device > shutdown on s2idle instead of changing the driver default. > > We use dmi matching for our current platform quirk list. I do not know > what the equivalent is for device-tree based platforms. Do you know? Hi Keith, IMO, the NVME driver is not associated with any device tree, Instead PCI driver is associated with device tree. So unlike ACPI based platform where we have platform specific DMI matching, we don't have equivalent check for DT based platform. Do we see any concern if we introduce a module param with default not set to quick suspend. For platform that need full shutdown durring resume , they can set it to quick suspend. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-09 21:17 ` nitirawa @ 2022-02-09 21:47 ` Keith Busch 0 siblings, 0 replies; 14+ messages in thread From: Keith Busch @ 2022-02-09 21:47 UTC (permalink / raw) To: nitirawa Cc: Vidya Sagar, rafael.j.wysocki, keith.busch, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On Thu, Feb 10, 2022 at 02:47:47AM +0530, nitirawa@codeaurora.org wrote: > IMO, the NVME driver is not associated with any device tree, Instead PCI > driver is associated with device tree. That may be good, though: the idle behavior isn't unqiue to nvme. It may be fine if PCI is the common layer to own this, as long as drivers can query it. > So unlike ACPI based platform where we have platform specific DMI matching, > we don't have equivalent check for DT based platform. Is there any existing kernel API a driver can call to uniquely identify such a platform? > Do we see any concern if we introduce a module param with default not set to > quick suspend. As of now, the idea was proposed and was not accepted. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-09 20:26 ` Keith Busch 2022-02-09 21:17 ` nitirawa @ 2022-02-10 4:11 ` Vidya Sagar 2022-02-10 5:40 ` Lukas Wunner 1 sibling, 1 reply; 14+ messages in thread From: Vidya Sagar @ 2022-02-10 4:11 UTC (permalink / raw) To: Keith Busch, robh+dt Cc: rafael.j.wysocki, keith.busch, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On 2/10/2022 1:56 AM, Keith Busch wrote: > External email: Use caution opening links or attachments > > > On Tue, Feb 01, 2022 at 09:52:28PM +0530, Vidya Sagar wrote: >> Hi Rafael & Christoph, >> My query is regarding the comment and the code that follows after it at >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/host/pci.c?h=v5.17-rc2#n3243 >> What I understood from it is that, there is an underlying assumption >> that the power to the devices is not removed during the suspend call. >> In the case of device-tree based platforms like Tegra194, power is >> indeed removed to the devices during suspend-resume process. Hence, the >> NVMe devices need to be taken through the shutdown path irrespective of >> whether the ASPM states are enabled or not. >> I would like to hear from you the best method to follow to achieve this. > > Christoph prefers to append quirks for platforms that need full device > shutdown on s2idle instead of changing the driver default. > > We use dmi matching for our current platform quirk list. I do not know > what the equivalent is for device-tree based platforms. Do you know? I'm afraid I don't. Rob, could you please help here? > ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-10 4:11 ` Vidya Sagar @ 2022-02-10 5:40 ` Lukas Wunner 2022-02-10 12:36 ` nitirawa 0 siblings, 1 reply; 14+ messages in thread From: Lukas Wunner @ 2022-02-10 5:40 UTC (permalink / raw) To: Vidya Sagar Cc: Keith Busch, robh+dt, rafael.j.wysocki, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On Thu, Feb 10, 2022 at 09:41:04AM +0530, Vidya Sagar wrote: > On 2/10/2022 1:56 AM, Keith Busch wrote: > > Christoph prefers to append quirks for platforms that need full device > > shutdown on s2idle instead of changing the driver default. > > > > We use dmi matching for our current platform quirk list. I do not know > > what the equivalent is for device-tree based platforms. Do you know? > > I'm afraid I don't. of_machine_is_compatible() ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Query related to shutting down NVMe during system suspend 2022-02-10 5:40 ` Lukas Wunner @ 2022-02-10 12:36 ` nitirawa 0 siblings, 0 replies; 14+ messages in thread From: nitirawa @ 2022-02-10 12:36 UTC (permalink / raw) To: Lukas Wunner, Keith Busch Cc: Vidya Sagar, Keith Busch, robh+dt, rafael.j.wysocki, hch, bhelgaas, mmaddireddy, kthota, sagar.tv, linux-pci, linux-kernel On 2022-02-10 11:10, Lukas Wunner wrote: > On Thu, Feb 10, 2022 at 09:41:04AM +0530, Vidya Sagar wrote: >> On 2/10/2022 1:56 AM, Keith Busch wrote: >> > Christoph prefers to append quirks for platforms that need full device >> > shutdown on s2idle instead of changing the driver default. >> > >> > We use dmi matching for our current platform quirk list. I do not know >> > what the equivalent is for device-tree based platforms. Do you know? >> >> I'm afraid I don't. > > of_machine_is_compatible() Thanks Lukas and keith . Yes it worked using of_machine_is_compatible as it checks root node of device tree for a given compatible value. @keith - I have posted the change using above API to enable nvme quick suspend quirks for sc7280 platform. Please can you review it. ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2022-02-10 12:37 UTC | newest] Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-02-01 16:22 Query related to shutting down NVMe during system suspend Vidya Sagar 2022-02-01 16:30 ` Keith Busch 2022-02-01 16:58 ` Vidya Sagar 2022-02-07 10:57 ` nitirawa 2022-02-07 12:11 ` Vidya Sagar 2022-02-07 15:44 ` nitirawa 2022-02-07 15:47 ` Keith Busch 2022-02-01 17:17 ` Rafael J. Wysocki 2022-02-09 20:26 ` Keith Busch 2022-02-09 21:17 ` nitirawa 2022-02-09 21:47 ` Keith Busch 2022-02-10 4:11 ` Vidya Sagar 2022-02-10 5:40 ` Lukas Wunner 2022-02-10 12:36 ` nitirawa
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).