LKML Archive on
help / color / mirror / Atom feed
From: Mika Westerberg <>
To: "Rafael J. Wysocki" <>
Cc: Linux PCI <>,
	Linux ACPI <>,
	Linux PM <>,
	LKML <>,
	Bjorn Helgaas <>,
	Kai-Heng Feng <>,
	Utkarsh H Patel <>,
	Koba Ko <>
Subject: Re: [PATCH v1.1 1/2] PCI: PM: Avoid forcing PCI_D0 for wakeup reasons inconsistently
Date: Fri, 30 Jul 2021 13:26:31 +0300	[thread overview]
Message-ID: <YQPT1y2hA+/UPReI@lahna> (raw)
In-Reply-To: <2593738.mvXUDI8C0e@kreacher>

On Thu, Jul 29, 2021 at 05:54:28PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <>
> It is inconsistent to return PCI_D0 from pci_target_state() instead
> of the original target state if 'wakeup' is true and the device
> cannot signal PME from D0.
> This only happens when the device cannot signal PME from the original
> target state and any shallower power states (including D0) and that
> case is effectively equivalent to the one in which PME singaling is
> not supported at all.  Since the original target state is returned in
> the latter case, make the function do that in the former one too.
> Link:
> Fixes: 666ff6f83e1d ("PCI/PM: Avoid using device_may_wakeup() for runtime PM")
> Reported-by: Mika Westerberg <>

Reviewed-by: Mika Westerberg <>
Tested-by: Mika Westerberg <>

  reply	other threads:[~2021-07-30 10:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29 14:46 [PATCH v1 0/2] PCI: PM: Fix handling of device that can only signal PME from D3cold Rafael J. Wysocki
2021-07-29 14:48 ` [PATCH v1 1/2] PCI: PM: Add special case handling for PCIe device wakeup Rafael J. Wysocki
2021-07-29 15:09   ` Rafael J. Wysocki
2021-07-29 15:54   ` [PATCH v1.1 1/2] PCI: PM: Avoid forcing PCI_D0 for wakeup reasons inconsistently Rafael J. Wysocki
2021-07-30 10:26     ` Mika Westerberg [this message]
2021-07-29 14:49 ` [PATCH v1 2/2] PCI: PM: Enable PME if it can be signaled from D3cold Rafael J. Wysocki
2021-07-30 10:28   ` Mika Westerberg
2021-07-30 12:13     ` Rafael J. Wysocki

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YQPT1y2hA+/UPReI@lahna \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH v1.1 1/2] PCI: PM: Avoid forcing PCI_D0 for wakeup reasons inconsistently' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).