From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: bhelgaas@google.com, koba.ko@canonical.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] PCI: Add helper to check if any of ancestor device support D3cold
Date: Thu, 24 Aug 2023 14:56:56 +0300 [thread overview]
Message-ID: <20230824115656.GW3465@black.fi.intel.com> (raw)
In-Reply-To: <20230824044645.423378-1-kai.heng.feng@canonical.com>
Hi,
On Thu, Aug 24, 2023 at 12:46:43PM +0800, Kai-Heng Feng wrote:
> In addition to nearest upstream bridge, driver may want to know if the
> entire hierarchy can be powered off to perform different action.
>
> So walk higher up the hierarchy to find out if any device has valid
> _PR3.
I'm not entirely sure this is good idea. The drivers should expect that
the power will be turned off pretty soon after device enters D3hot. Also
_PR3 is not PCI concept it's ACPI concept so API like this would only
work on systems with ACPI.
next prev parent reply other threads:[~2023-08-24 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 4:46 [PATCH 1/3] PCI: Add helper to check if any of ancestor device support D3cold Kai-Heng Feng
2023-08-24 4:46 ` [PATCH 2/3] PCI/AER: Disable AER service on suspend Kai-Heng Feng
2023-08-24 4:46 ` Kai-Heng Feng
2023-08-24 4:46 ` [PATCH 3/3] PCI/DPC: Disable DPC " Kai-Heng Feng
2023-08-24 4:46 ` Kai-Heng Feng
2023-08-24 11:56 ` Mika Westerberg [this message]
2023-08-24 13:46 ` [PATCH 1/3] PCI: Add helper to check if any of ancestor device support D3cold Kai-Heng Feng
2023-08-25 5:29 ` Mika Westerberg
2023-08-25 5:43 ` Kai-Heng Feng
2023-08-25 6:39 ` Mika Westerberg
2023-08-26 13:11 ` Bjorn Helgaas
2023-08-28 7:29 ` Kai-Heng Feng
2023-08-28 16:23 ` Bjorn Helgaas
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=20230824115656.GW3465@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=kai.heng.feng@canonical.com \
--cc=koba.ko@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.