[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220209214718.GC1616420@dhcp-10-100-145-180.wdc.com>
Date: Wed, 9 Feb 2022 13:47:18 -0800
From: Keith Busch <kbusch@...nel.org>
To: nitirawa@...eaurora.org
Cc: Vidya Sagar <vidyas@...dia.com>, rafael.j.wysocki@...el.com,
keith.busch@...el.com, hch@....de, bhelgaas@...gle.com,
mmaddireddy@...dia.com, kthota@...dia.com, sagar.tv@...il.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Query related to shutting down NVMe during system suspend
On Thu, Feb 10, 2022 at 02:47:47AM +0530, nitirawa@...eaurora.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.
Powered by blists - more mailing lists