linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>, bhelgaas@google.com
Cc: mika.westerberg@linux.intel.com, linux-pci@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Pearson <mpearson-lenovo@squebb.ca>
Subject: Re: [PATCH] PCI/PM: Put devices to low power state on shutdown
Date: Fri, 12 Jul 2024 09:59:05 -0500	[thread overview]
Message-ID: <9d2f1619-1c61-4e8c-b28d-d4eddefa45c3@amd.com> (raw)
In-Reply-To: <20240712062411.35732-1-kai.heng.feng@canonical.com>

On 7/12/2024 1:24, Kai-Heng Feng wrote:
> Some laptops wake up after poweroff when HP Thunderbolt Dock G4 is
> connected.
> 
> The following error message can be found during shutdown:
> pcieport 0000:00:1d.0: AER: Correctable error message received from 0000:09:04.0
> pcieport 0000:09:04.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
> pcieport 0000:09:04.0:   device [8086:0b26] error status/mask=00000080/00002000
> pcieport 0000:09:04.0:    [ 7] BadDLLP
> 
> Calling aer_remove() during shutdown can quiesce the error message,
> however the spurious wakeup still happens.
> 
> The issue won't happen if the device is in D3 before system shutdown, so
> putting device to low power state before shutdown to solve the issue.
> 
> I don't have a sniffer so this is purely guesswork, however I believe
> putting device to low power state it's the right thing to do.
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=219036
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>

This is directionally very similar to the proposal that I had at the end 
of last year.

https://lore.kernel.org/linux-pci/20231213182656.6165-1-mario.limonciello@amd.com/#t

I definitely think we should be aiming at all devices that don't wake 
the system as being in D3 at shutdown.

> ---
>   drivers/pci/pci-driver.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index af2996d0d17f..4c6f66f3eb54 100644
> --- a/drivers/pci/pci-driver.c
> +++ b/drivers/pci/pci-driver.c
> @@ -510,6 +510,14 @@ static void pci_device_shutdown(struct device *dev)
>   	if (drv && drv->shutdown)
>   		drv->shutdown(pci_dev);
>   
> +	/*
> +	 * If driver already changed device's power state, it can mean the
> +	 * wakeup setting is in place, or a workaround is used. Hence keep it
> +	 * as is.
> +	 */
> +	if (!kexec_in_progress && pci_dev->current_state == PCI_D0)
> +		pci_prepare_to_sleep(pci_dev);
> +
>   	/*
>   	 * If this is a kexec reboot, turn off Bus Master bit on the
>   	 * device to tell it to not continue to do DMA. Don't touch


  reply	other threads:[~2024-07-12 14:59 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 [this message]
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
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=9d2f1619-1c61-4e8c-b28d-d4eddefa45c3@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=bhelgaas@google.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mpearson-lenovo@squebb.ca \
    /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).