From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Kai-Heng Feng <kaihengfeng@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] PCI/PM: Put devices to low power state on shutdown
Date: Sun, 15 Sep 2024 10:14:06 +0300 [thread overview]
Message-ID: <20240915071406.GR275077@black.fi.intel.com> (raw)
In-Reply-To: <12857e01-f6cc-4489-935b-7e6c354706e9@amd.com>
Hi,
On Fri, Sep 13, 2024 at 03:33:33PM -0500, Mario Limonciello wrote:
> > I know this is about entering S5 (power off) but I wonder if simply
> > disabling the device (I/O, MMIO and bus mastering) could stop it from
> > waking up?
>
> To me, it's a two-fold problem. The device consumes too much power, and the
> device issues interrupts when system is in S5.
>
> Putting it in D3 should nip both, disabling the device might help the
> latter.
>
> I did the same thing a vendor did for KH where I double checked the waveform
> at S5 and could see the devices still in D0.
>
> Or do you think that by the device being in D0 but disabled should be enough
> for decreasing power?
No, not about power but just to solve the issue here. I'm not objecting
putting the device into D3 instead on the grounds that if Windows does
this then probably it is safe or us to do as well and also avoids
possible untested paths in the firmware side too.
Strictly based on ACPI spec [1] there is no such requirement though.
[1] https://uefi.org/specs/ACPI/6.5/16_Waking_and_Sleeping.html#transitioning-from-the-working-to-the-soft-off-state
next prev parent reply other threads:[~2024-09-15 7:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 6:24 [PATCH] PCI/PM: Put devices to low power state on shutdown Kai-Heng Feng
2024-07-12 14:59 ` Mario Limonciello
2024-08-22 19:28 ` Mario Limonciello
2024-08-26 12:03 ` Kai-Heng Feng
2024-09-11 14:08 ` Mario Limonciello
2024-09-11 19:05 ` Bjorn Helgaas
2024-09-11 19:16 ` Mario Limonciello
2024-09-11 19:38 ` Mario Limonciello
2024-09-12 7:02 ` Kai-Heng Feng
2024-09-12 13:10 ` Mario Limonciello
2024-10-04 4:33 ` Chia-Lin Kao (AceLan)
2024-10-04 9:26 ` Kai-Heng Feng
2024-09-12 3:00 ` Kai-Heng Feng
2024-09-12 16:57 ` Bjorn Helgaas
2024-09-13 6:00 ` Kai-Heng Feng
2024-09-13 8:01 ` Mika Westerberg
2024-09-13 20:33 ` Mario Limonciello
2024-09-15 7:14 ` Mika Westerberg [this message]
2024-10-09 22:24 ` Bjorn Helgaas
2024-10-10 4:52 ` Mika Westerberg
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=20240915071406.GR275077@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kaihengfeng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rjw@rjwysocki.net \
/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).