Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp997429pxb; Thu, 17 Feb 2022 21:02:04 -0800 (PST) X-Google-Smtp-Source: ABdhPJwmmTdB3mDgr0S/vtSU0KLwJammZR4O53mru9KDXYK7lPsQqAehqzfrLbWFT71ut2CqA+QQ X-Received: by 2002:a17:906:b005:b0:6b4:8861:597b with SMTP id v5-20020a170906b00500b006b48861597bmr4887639ejy.238.1645160524692; Thu, 17 Feb 2022 21:02:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645160524; cv=none; d=google.com; s=arc-20160816; b=nKCE5l+I+hHAh5CqO/Uenwa1V6KJJ0iwpt01qAYU3zcvui+c1LhCyLTUnKh0DLoDCf Q0NcSSYzB1fXv5ED/B+aHEUqJzenSk52wL6yT+NmSgdOzqoI8j6ITm0yrdpQoygx95x2 4+KLBlpFXP2paoTlkt62tjk0qDCK+eFmbUiCJqozyszrd5l6PCaTBNHICSXbcs5MyqI5 I1IXw8QboLzUbTnrhwdngWIcRRdygUG1YnlEIvtrJaiRgOxoa+iEMPYpryPvx+j4bFJI Io/T1S50eIHxF95S3QA/+mP7hCm++UUAXtXvMeHDSSHelxUC0Gzc5KyQ3aS5L4PBkxqS /gUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=N4SBtlJWrq00yTtKaNPg2aC+ZXobniPGW+A0ZOAvpx8=; b=Ow5VYc1a17Ur0wjhpFq9YOaoccn4TLSkjtaXXk87sdNEBABrFjVu735EXnhTsK3D/P D5tawacKyAOn9TxHL7GnF5nDaxzaU1Mn/5lRLtfiW+gOAKfU1Rem6nR8Ld7SSB6UgArh YhmQgN/e5vujSMQtBMJNSKQHdW9TekyZgDFsqiWA59ZYYHusBt6poiM5P309lM1I1rno fUYa+AXACaE9pBTNl9wMb0iPmajMQw/olNcnX55WAn+fwa92+DUz43BHLn3qfEBlXzla PX8EOA3R5lMImA4lUq8zz/sHMO8BwrgpBKZnpZgbpzI1mVtzeenFK0iDgnnwX/x4+xp2 ckDA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="A2kBhM/q"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h7si2747880ede.578.2022.02.17.21.01.42; Thu, 17 Feb 2022 21:02:04 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="A2kBhM/q"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230005AbiBREvh (ORCPT + 99 others); Thu, 17 Feb 2022 23:51:37 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:44590 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229986AbiBREv0 (ORCPT ); Thu, 17 Feb 2022 23:51:26 -0500 Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F2E6238D98; Thu, 17 Feb 2022 20:51:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645159870; x=1676695870; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=7NweWA9u8MLHzRnDn77tVJVW+/OijRX/EBVVwLg8Lh0=; b=A2kBhM/qK8sI3luzIDXOg6H/1XIfwmw0C9J2oPsD4OP8IuEqrPHf3Wqn xYD2/KkxiBxQwzRBlNSnVSHzmGWKfnA4W4kjmfR+yLbeXgEjoxqgwwVTx h6MCTZLg1rEiqcz7fpuQYtGHWfdA9vakeVAnxdtbChQOCIzE2QbqJOxbd nUHY492B9BTym3RfOEoIGNESas90okIZR+IVzd54+4nartZC6yD0X1dvo vlGA18ysviB/lvkJ0VUq8qdPtLAFcQBgMvMKaBd7r2/EPIBUseTIeTsHO 2B86vIE4FIkfDh+uz9+VG9TVmmy1M35/1BymAzTdnOSJBt60mdpRsMHSJ Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10261"; a="311793166" X-IronPort-AV: E=Sophos;i="5.88,377,1635231600"; d="scan'208";a="311793166" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Feb 2022 20:51:10 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.88,377,1635231600"; d="scan'208";a="572162984" Received: from linux.intel.com ([10.54.29.200]) by orsmga001.jf.intel.com with ESMTP; 17 Feb 2022 20:51:10 -0800 Received: from debox1-desk4.lan (unknown [10.251.23.8]) by linux.intel.com (Postfix) with ESMTP id 385DD580C70; Thu, 17 Feb 2022 20:51:10 -0800 (PST) From: "David E. Box" To: nirmal.patel@linux.intel.com, jonathan.derrick@linux.dev, lorenzo.pieralisi@arm.com, hch@infradead.org, kw@linux.com, robh@kernel.org, bhelgaas@google.com, david.e.box@linux.intel.com, michael.a.bottini@linux.intel.com, rafael@kernel.org, me@adhityamohan.in Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH V5 3/3] PCI: vmd: Configure PCIe ASPM and LTR Date: Thu, 17 Feb 2022 20:50:56 -0800 Message-Id: <20220218045056.333799-4-david.e.box@linux.intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220218045056.333799-1-david.e.box@linux.intel.com> References: <20220218045056.333799-1-david.e.box@linux.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Currently, PCIe ports reserved for VMD use are not visible to BIOS and therefore not configured to enable PCIE ASPM. Additionally, PCIE LTR values may be left unset since BIOS will set a default maximum LTR value on endpoints to ensure that misconfigured devices don't block SoC power management. Lack of this programming results in high power consumption on laptops as reported in bugzilla [1]. For currently affected products, use pci_enable_default_link_state to set the allowed link states for devices on the root ports. Also set the LTR value to the maximum value needed for the SoC. Per the VMD hardware team future products using VMD will enable BIOS configuration of these capabilities. This solution is a workaround for current products that mainly targets laptops. Support is not provided if a switch is used nor for hotplug. [1] https://bugzilla.kernel.org/show_bug.cgi?id=213717 Signed-off-by: Michael Bottini Signed-off-by: David E. Box --- V5 - Provide the LTR value as driver data. - Use DWORD for the config space write to avoid PCI WORD access bug. - Set ASPM links firsts, enabling all link states, before setting a default LTR if the capability is present - Add kernel message that VMD is setting the device LTR. V4 - Refactor vmd_enable_apsm() to exit early, making the lines shorter and more readable. Suggested by Christoph. V3 - No changes V2 - Use return status to print pci_info message if ASPM cannot be enabled. - Add missing static declaration, caught by lkp@intel.com drivers/pci/controller/vmd.c | 48 +++++++++++++++++++++++++++++++++++- 1 file changed, 47 insertions(+), 1 deletion(-) diff --git a/drivers/pci/controller/vmd.c b/drivers/pci/controller/vmd.c index a582c351b461..eac379c80cd7 100644 --- a/drivers/pci/controller/vmd.c +++ b/drivers/pci/controller/vmd.c @@ -67,10 +67,19 @@ enum vmd_features { * interrupt handling. */ VMD_FEAT_CAN_BYPASS_MSI_REMAP = (1 << 4), + + /* + * Enable ASPM on the PCIE root ports and set the default LTR of the + * storage devices on platforms where these values are not configured by + * BIOS. This is needed for laptops, which require these settings for + * proper power management of the SoC. + */ + VMD_FEAT_BIOS_PM_QUIRK = (1 << 5), }; struct vmd_device_data { enum vmd_features features; + u16 ltr; }; static DEFINE_IDA(vmd_instance_ida); @@ -714,6 +723,38 @@ static void vmd_copy_host_bridge_flags(struct pci_host_bridge *root_bridge, vmd_bridge->native_dpc = root_bridge->native_dpc; } +/* + * Enable ASPM and LTR settings on devices that aren't configured by BIOS. + */ +static int vmd_pm_enable_quirk(struct pci_dev *pdev, void *userdata) +{ + struct vmd_device_data *info = userdata; + u32 ltr_reg; + int pos; + + if (!(info->features & VMD_FEAT_BIOS_PM_QUIRK)) + return 0; + + pci_enable_default_link_state(pdev, PCIE_LINK_STATE_ALL); + + pos = pci_find_ext_capability(pdev, PCI_EXT_CAP_ID_LTR); + if (!pos) + return 0; + + /* + * If the LTR capability is present, set the default values to the + * maximum required by the platform to allow the deepest power + * management savings. Write this as a single DWORD where the lower word + * is the max snoop latency and the upper word is the max non-snoop + * latency. + */ + pci_info(pdev, "VMD: Setting a default LTR\n"); + ltr_reg = (info->ltr << 16) | info->ltr; + pci_write_config_dword(pdev, pos + PCI_LTR_MAX_SNOOP_LAT, ltr_reg); + + return 0; +} + static int vmd_enable_domain(struct vmd_dev *vmd, struct vmd_device_data *info) { struct pci_sysdata *sd = &vmd->sysdata; @@ -867,6 +908,8 @@ static int vmd_enable_domain(struct vmd_dev *vmd, struct vmd_device_data *info) pci_reset_bus(child->self); pci_assign_unassigned_bus_resources(vmd->bus); + pci_walk_bus(vmd->bus, vmd_pm_enable_quirk, info); + /* * VMD root buses are virtual and don't return true on pci_is_pcie() * and will fail pcie_bus_configure_settings() early. It can instead be @@ -1012,7 +1055,10 @@ static const struct vmd_device_data vmd_28c0_data = { static const struct vmd_device_data vmd_467f_data = { .features = VMD_FEAT_HAS_MEMBAR_SHADOW_VSCAP | VMD_FEAT_HAS_BUS_RESTRICTIONS | - VMD_FEAT_OFFSET_FIRST_VECTOR, + VMD_FEAT_OFFSET_FIRST_VECTOR | + VMD_FEAT_BIOS_PM_QUIRK, + /* 3145728 ns (LatencyScale of 1048576 ns with a LatencyValue of 3) */ + .ltr = 0x1003, }; static const struct pci_device_id vmd_ids[] = { -- 2.25.1