Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp973603ybj; Tue, 5 May 2020 10:38:55 -0700 (PDT) X-Google-Smtp-Source: APiQypKy0yqteedpeKZg4uqUTSg/lgq95NuNajdFdP7Ylxe8mQWfsj/Io+kTwZrDpodJGvR6Ly5l X-Received: by 2002:a17:907:9481:: with SMTP id dm1mr4031490ejc.268.1588700335190; Tue, 05 May 2020 10:38:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588700335; cv=none; d=google.com; s=arc-20160816; b=diRxBp01Fu/SoqrPq5t/RPI68UFsQzDifb5S+17MOazpvn+VeyPKvXx4SM9yA/Zvc1 gASiRpGixknxQ0CmuO9FwqGl/QdMMgtW7bj8RZped9M9bkECz1U5O3f6Usd5TIMcj/22 VsR1fFcf1avENfMU9TqA29l9B+ETjqV+edT6Wdeoz6/nkO5WPyOhmBJAMlJlIrab8mOd VjM7+JojyW5yeqRBwj9iEj+lb3KmxM4GpyhAXw+69Fz60l8n/rVb0MySx1TI83RhdgHn QJ+SZJ+zJzp9ZDOPkOhrw1dXVGsOeMM0Fu4afymo8G55cyVCJMn0b2wi90eDrf7oxlgA efew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=NwTjotBtYvqulOkkuANSi2WxNr3Xikr3mvfp2hfCsTU=; b=Dkc4ZKTMWjbq7Q5EFLURaajnHDVKAYVWHzBCB7TN8iMx91VHEBit5WhCbTCBzH8qbA d1s8u6vDraLGRIG7nc7RUOtQADGnVT+RuaUqUBFKj0txLUFouF69Yya5Xk8vFnHTW7cf I7+rdDf1HhXanUAPXd16J+6XIj0K2JwMManHTnQ91UTtXlDdRAWPlsvnLewqo1Lo8sw+ zySQzays3JZrUkTbVFCKPLeaAXWz0Rm7SXZoRasnYS3ZpyQqUk5LTVfhvufggdH/CHJt 1f5aplXrnF31pWb0TrpZxgyqwIHsTMWh2wFuMX+fC8v/prIY5yl2To2UrZU+Ywf7sNQo 70PQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t14si1569808edi.331.2020.05.05.10.38.31; Tue, 05 May 2020 10:38:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730159AbgEERgk (ORCPT + 99 others); Tue, 5 May 2020 13:36:40 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:35293 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729663AbgEERgk (ORCPT ); Tue, 5 May 2020 13:36:40 -0400 Received: from 61-220-137-37.hinet-ip.hinet.net ([61.220.137.37] helo=localhost) by youngberry.canonical.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1jW1Sk-0000yL-9Y; Tue, 05 May 2020 17:34:35 +0000 From: Kai-Heng Feng To: bhelgaas@google.com Cc: Kai-Heng Feng , Heiner Kallweit , "Rafael J. Wysocki" , Keith Busch , Mika Westerberg , Chris Packham , Yicong Yang , Krzysztof Wilczynski , linux-pci@vger.kernel.org (open list:PCI SUBSYSTEM), linux-kernel@vger.kernel.org (open list) Subject: [PATCH v3] PCI/ASPM: Enable ASPM for bridge-to-bridge link Date: Wed, 6 May 2020 01:34:21 +0800 Message-Id: <20200505173423.26968-1-kai.heng.feng@canonical.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20200505122801.12903-1-kai.heng.feng@canonical.com> References: <20200505122801.12903-1-kai.heng.feng@canonical.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The TI PCIe-to-PCI bridge prevents the Intel SoC from entering power state deeper than PC3 due to disabled ASPM, consumes lots of unnecessary power. On Windows ASPM L1 is enabled on the device and its upstream bridge, so it can make the Intel SoC reach PC8 or PC10 to save lots of power. In short, ASPM always gets disabled on bridge-to-bridge link. The special case was part of first ASPM introduction patch, commit 7d715a6c1ae5 ("PCI: add PCI Express ASPM support"). However, it didn't explain why ASPM needs to be disabled in special bridge-to-bridge case. Let's remove the the special case, as PCIe spec already envisioned ASPM on bridge-to-bridge link. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=207571 Signed-off-by: Kai-Heng Feng --- v3: - Remove the special case completely. v2: - Enable ASPM on root complex <-> bridge <-> bridge, instead of using quirk. drivers/pci/pcie/aspm.c | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c index 2378ed692534..b17e5ffd31b1 100644 --- a/drivers/pci/pcie/aspm.c +++ b/drivers/pci/pcie/aspm.c @@ -628,16 +628,6 @@ static void pcie_aspm_cap_init(struct pcie_link_state *link, int blacklist) /* Setup initial capable state. Will be updated later */ link->aspm_capable = link->aspm_support; - /* - * If the downstream component has pci bridge function, don't - * do ASPM for now. - */ - list_for_each_entry(child, &linkbus->devices, bus_list) { - if (pci_pcie_type(child) == PCI_EXP_TYPE_PCI_BRIDGE) { - link->aspm_disable = ASPM_STATE_ALL; - break; - } - } /* Get and check endpoint acceptable latencies */ list_for_each_entry(child, &linkbus->devices, bus_list) { -- 2.17.1