From: Keith Busch <kbusch@kernel.org>
To: nitirawa@codeaurora.org
Cc: Vidya Sagar <vidyas@nvidia.com>,
rafael.j.wysocki@intel.com, keith.busch@intel.com, hch@lst.de,
bhelgaas@google.com, mmaddireddy@nvidia.com, kthota@nvidia.com,
sagar.tv@gmail.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Query related to shutting down NVMe during system suspend
Date: Wed, 9 Feb 2022 13:47:18 -0800 [thread overview]
Message-ID: <20220209214718.GC1616420@dhcp-10-100-145-180.wdc.com> (raw)
In-Reply-To: <bc80ec7d1ca2c56feded1a6848c285ef@codeaurora.org>
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.
next prev parent reply other threads:[~2022-02-09 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2022-02-10 4:11 ` Vidya Sagar
2022-02-10 5:40 ` Lukas Wunner
2022-02-10 12:36 ` nitirawa
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=20220209214718.GC1616420@dhcp-10-100-145-180.wdc.com \
--to=kbusch@kernel.org \
--cc=bhelgaas@google.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=nitirawa@codeaurora.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sagar.tv@gmail.com \
--cc=vidyas@nvidia.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;
as well as URLs for NNTP newsgroup(s).