All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Kedar A Dongre <kedar.a.dongre@intel.com>,
	linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] PCI: Blacklist power management of Gigabyte X299 DESIGNARE EX PCIe ports
Date: Wed, 5 Dec 2018 15:46:42 +0200	[thread overview]
Message-ID: <20181205134642.GR2469@lahna.fi.intel.com> (raw)
In-Reply-To: <20181205132214.kaojqse4dbcvodxz@wunner.de>

On Wed, Dec 05, 2018 at 02:22:14PM +0100, Lukas Wunner wrote:
> On Wed, Dec 05, 2018 at 12:40:29PM +0200, Mika Westerberg wrote:
> > On Wed, Dec 05, 2018 at 10:48:18AM +0100, Lukas Wunner wrote:
> > > Does the root port have a _RMV and/or _SUN object?  We could e.g.
> > > disallow runtime PM for any bridge with _RMV present and the HPC
> > > bit not set in the Slot Capabilities.
> > 
> > Unfortunately it does not have either of those methods :/ It pretty much
> > looks like a "normal root port" from OS perspective.
> > 
> > Below is the ASL related to the root port (RP05) in question:
> 
> The information might be buried in the Device Labeling DSM but I can't
> make sense of it because I only have access to the PCI Firmware Spec 3.0,
> which is too old.

Good point. I have 3.2 but only ones in that _DSM are:

  4 = PCI Bus Capabilities
  6 = LTR Maximum Latency
  8 = Avoid power-on Reset Delay Duplication on Sx Resume
  9 = Device Readiness Durations

Only thing that could be relevant is 4 (PCI Bus Capabilities) but I
don't see anything in the spec saying it could be hot plug capable :(

  reply	other threads:[~2018-12-05 13:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 11:20 [PATCH] PCI: Blacklist power management of Gigabyte X299 DESIGNARE EX PCIe ports Mika Westerberg
2018-12-04 17:55 ` Rafael J. Wysocki
2018-12-04 18:34   ` Mika Westerberg
2018-12-04 20:40 ` Lukas Wunner
2018-12-05  9:20   ` Mika Westerberg
2018-12-05  9:48     ` Lukas Wunner
2018-12-05 10:40       ` Mika Westerberg
2018-12-05 13:22         ` Lukas Wunner
2018-12-05 13:46           ` Mika Westerberg [this message]
2018-12-14  9:24 ` Mika Westerberg
2018-12-17 20:28 ` Bjorn Helgaas
2018-12-18  8:55   ` Mika Westerberg
2018-12-18 20:58     ` Bjorn Helgaas
2018-12-19 13:23       ` Mika Westerberg
2018-12-19 14:45         ` Bjorn Helgaas
2018-12-19 15:15           ` Mika Westerberg
2018-12-19 17:09             ` Lukas Wunner
2018-12-20 10:06               ` Mika Westerberg
2018-12-20 10:23                 ` 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:
  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=20181205134642.GR2469@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=kedar.a.dongre@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --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 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.