From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Limonciello, Mario" <mario.limonciello@amd.com>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>,
Prike Liang <Prike.Liang@amd.com>,
rrangel@chromium.org,
"David E. Box" <david.e.box@linux.intel.com>,
Shyam-sundar S-k <Shyam-sundar.S-k@amd.com>,
Alexander Deucher <Alexander.Deucher@amd.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH v2] nvme: Look for StorageD3Enable on companion ACPI device instead
Date: Thu, 27 May 2021 19:28:58 +0200 [thread overview]
Message-ID: <20210527172857.GA7426@lst.de> (raw)
In-Reply-To: <20210527165844.GC3706388@dhcp-10-100-145-180.wdc.com>
[adding Rafael]
On Thu, May 27, 2021 at 09:58:44AM -0700, Keith Busch wrote:
> EXPORT_SYMBOL_GPL(acpi_dev_pm_attach);
> +
> +bool acpi_storage_d3(struct device *dev)
This need a really good kerneldoc comment. Not like pci_pr3_present
which somehow made it into the PCI core, but has not explanation
whatsoever..
> +{
> + struct acpi_device *adev;
> + u8 val;
> +
> + /*
> + * Look for _DSD property specifying that the storage device on the port
> + * must use D3 to support deep platform power savings during
> + * suspend-to-idle.
> + */
This is part of what should got into the kerneldoc
> + adev = ACPI_COMPANION(dev);
> + if (!adev)
> + return false;
> + if (fwnode_property_read_u8(acpi_fwnode_handle(adev), "StorageD3Enable",
> + &val))
> + return false;
> + return val == 1;
> +}
adev could be initialized at declaration time.
Also any chance we could have acpi_fwnode_property_read_* helpers
that include the NULL check and the acpi_fwnode_handle conversion which
seems to be boilerplated all over?
Also I wonder if having this only in ACPI is a good idea. What when
we get the same thing in OF? Isn't this something that the PM layer
should tell the device when calling ->suspend?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-05-27 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 13:59 [PATCH v2] nvme: Look for StorageD3Enable on companion ACPI device instead Mario Limonciello
2021-05-27 14:35 ` Christoph Hellwig
2021-05-27 14:44 ` Limonciello, Mario
2021-05-27 15:52 ` Bjorn Helgaas
2021-05-27 16:58 ` Keith Busch
2021-05-27 17:03 ` Limonciello, Mario
2021-05-27 17:28 ` Christoph Hellwig [this message]
2021-05-27 15:53 ` Raul Rangel
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=20210527172857.GA7426@lst.de \
--to=hch@lst.de \
--cc=Alexander.Deucher@amd.com \
--cc=Prike.Liang@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=axboe@fb.com \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mario.limonciello@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