From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8F705C04EB9 for ; Wed, 5 Dec 2018 13:22:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4B8B920850 for ; Wed, 5 Dec 2018 13:22:18 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4B8B920850 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=wunner.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-pci-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727006AbeLENWR (ORCPT ); Wed, 5 Dec 2018 08:22:17 -0500 Received: from bmailout3.hostsharing.net ([176.9.242.62]:43293 "EHLO bmailout3.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726937AbeLENWR (ORCPT ); Wed, 5 Dec 2018 08:22:17 -0500 Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.hostsharing.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by bmailout3.hostsharing.net (Postfix) with ESMTPS id 3175A101D66FB; Wed, 5 Dec 2018 14:22:15 +0100 (CET) Received: by h08.hostsharing.net (Postfix, from userid 100393) id DB19812140; Wed, 5 Dec 2018 14:22:14 +0100 (CET) Date: Wed, 5 Dec 2018 14:22:14 +0100 From: Lukas Wunner To: Mika Westerberg Cc: Bjorn Helgaas , "Rafael J. Wysocki" , Kedar A Dongre , linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: [PATCH] PCI: Blacklist power management of Gigabyte X299 DESIGNARE EX PCIe ports Message-ID: <20181205132214.kaojqse4dbcvodxz@wunner.de> References: <20181204112048.35378-1-mika.westerberg@linux.intel.com> <20181204204049.4zr7onei267t4pic@wunner.de> <20181205092034.GI2469@lahna.fi.intel.com> <20181205094818.jmdy2mg6b6is7jy3@wunner.de> <20181205104029.GL2469@lahna.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181205104029.GL2469@lahna.fi.intel.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org 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. Thanks, Lukas