Message ID | 20230320212029.3154407-1-david.e.box@linux.intel.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:604a:0:0:0:0:0 with SMTP id j10csp1449541wrt; Mon, 20 Mar 2023 14:37:26 -0700 (PDT) X-Google-Smtp-Source: AK7set+8pNWrr/yhwDSxiVl+URtfX34CETxNzpel1prdoX+y7OwOjbPorU25biMXm1PC+6c8BqxU X-Received: by 2002:aa7:9e04:0:b0:627:ef23:1f95 with SMTP id y4-20020aa79e04000000b00627ef231f95mr195031pfq.31.1679348246193; Mon, 20 Mar 2023 14:37:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679348246; cv=none; d=google.com; s=arc-20160816; b=HHZQqKEpipiqgYJLZoP2aDcUD8U8g9ALDYFszO/8tiRkWMtzQ0dsnqBm/jAfbiF/lv xhw3XK2RwswVkDcyXlu2Ppwri4dblnmn3YsabF10mCurtwaD21+yux9ySR8s6PhN9shJ /BnF8cJsmVaaTZDQJeL1tLehj3wfGwWO6ZJChKzdtJ3ZQNxdTiJKyyMCMg7ye1vKVz5m H7W7YFtpXlUkw0+YxpDrGO5ZK02NZwrb0MpURM5/s6JmiteZtIyosQW5pBdKZ0sUFZXd 4mt6onpD5njkBwregzkcxZGDu0FE3+dHZhM5RuMDjL2tuJabFR/gN/cj3t+Uc+orO4oI ECNw== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=9CZjzeRb6oFXMwbKp4zDByE1r9khsrkzRXKTObqDhPE=; b=E7qDBvpy9TLAc+8qBE8ULIBQYb9Nd2KV4x5DRpyFiuDgY58rZA1tp8ZNpc4Z4YIG7n n4qYDTlwBMfknFe6OEuQuxwT5PSFh4JfkqZJEqIrfRkCTUAf4Ujlc6g2/3i5xo+ENvAH IYuhmuHucnN7PFWId/RnpO9IKYkoAPVFeCYlZH5YOtE4BECyANQ5RdXCtp7Zh0J1kBqe FzyE7iOtP0OR1vNxw4sQw83KI8qw8buZuDunLuw1O/LwKaJSmEToQvXDs0cQYaeN6kCz 04ogMVbokZRRKOjCP0HhiBRHUb8mqDbr7aVw99zNgUHUShyjgkSNMFqy159RpVRL0Yzb /YdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=hqVgUx+z; 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: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w4-20020a656944000000b0050fa589bc9esi447333pgq.592.2023.03.20.14.37.13; Mon, 20 Mar 2023 14:37:26 -0700 (PDT) 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=hqVgUx+z; 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 S230093AbjCTVUh (ORCPT <rfc822;pusanteemu@gmail.com> + 99 others); Mon, 20 Mar 2023 17:20:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41634 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229819AbjCTVUc (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 20 Mar 2023 17:20:32 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA5FB2887D; Mon, 20 Mar 2023 14:20:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1679347231; x=1710883231; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=7xQHgXbzZUle4rIgGnDA5qyL/krFHQPTUEfjR3Qvmg8=; b=hqVgUx+zFEatCoEdkpRFHWfnHddunI7CQduuktFIwOzY7sxTkKRgQK5y p7D2zwE0ueu2A0/sSkgE863NHdsbNBGvE3KOKnm/Cem5hzUj/liT6ixAN MvIqb7kSVmMbnlHEaBrWsH3Z8ueSBfHv0Zfs6ptgbxS09arFWGrI3/Q36 w2IT3DzuJddlA71nW/vLkGpP8hIdio8FG3GRmMrddaUUBajIuQEYn3rkD d+lyNqMekUlDFhk8RxfjPfOoffa8TW+qU16CabtBM9QW5+B60EKuzzIYf D01fHxwkWS9hedoQ1Z5UDIcL34AaRO4ppgmwgAXOpT+npLayaxMrA9mu0 g==; X-IronPort-AV: E=McAfee;i="6600,9927,10655"; a="337498886" X-IronPort-AV: E=Sophos;i="5.98,276,1673942400"; d="scan'208";a="337498886" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Mar 2023 14:20:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10655"; a="674565826" X-IronPort-AV: E=Sophos;i="5.98,276,1673942400"; d="scan'208";a="674565826" Received: from linux.intel.com ([10.54.29.200]) by orsmga007.jf.intel.com with ESMTP; 20 Mar 2023 14:20:31 -0700 Received: from debox1-desk4.intel.com (unknown [10.251.19.209]) by linux.intel.com (Postfix) with ESMTP id EDEDF580110; Mon, 20 Mar 2023 14:20:30 -0700 (PDT) From: "David E. Box" <david.e.box@linux.intel.com> To: irenic.rajneesh@gmail.com, rajvi.jingar@linux.intel.com, david.e.box@linux.intel.com, hdegoede@redhat.com, markgross@kernel.org, andy.shevchenko@gmail.com Cc: linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org Subject: [PATCH] platform/x86/intel/pmc: Alder Lake PCH slp_s0_residency fix Date: Mon, 20 Mar 2023 14:20:29 -0700 Message-Id: <20230320212029.3154407-1-david.e.box@linux.intel.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.3 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 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1760924266713718280?= X-GMAIL-MSGID: =?utf-8?q?1760924266713718280?= |
Series |
platform/x86/intel/pmc: Alder Lake PCH slp_s0_residency fix
|
|
Commit Message
David E. Box
March 20, 2023, 9:20 p.m. UTC
From: Rajvi Jingar <rajvi.jingar@linux.intel.com> For platforms with Alder Lake PCH (Alder Lake S and Raptor Lake S) the slp_s0_residency attribute has been reporting the wrong value. Unlike other platforms, ADL PCH does not have a counter for the time that the SLP_S0 signal was asserted. Instead, firmware uses the aggregate of the Low Power Mode (LPM) substate counters as the S0ix value. Since the LPM counters run at a different frequency, this lead to misreporting of the S0ix time. Add a check for Alder Lake PCH and adjust the frequency accordingly when display slp_s0_residency. Fixes: bbab31101f44 ("platform/x86/intel: pmc/core: Add Alderlake support to pmc core driver") Signed-off-by: Rajvi Jingar <rajvi.jingar@linux.intel.com> Signed-off-by: David E. Box <david.e.box@linux.intel.com> --- drivers/platform/x86/intel/pmc/core.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) base-commit: 02c464b73645404654359ad21f368a13735e2850
Comments
Looks good to me. Just a nit, maybe change the subject to "Fix Alder Lake S0ix reporting" or something like that. Reviewed-by: Rajneesh Bhardwaj <irenic.rajneesh@gmail.com> On Mon, Mar 20, 2023 at 5:20 PM David E. Box <david.e.box@linux.intel.com> wrote: > > From: Rajvi Jingar <rajvi.jingar@linux.intel.com> > > For platforms with Alder Lake PCH (Alder Lake S and Raptor Lake S) the > slp_s0_residency attribute has been reporting the wrong value. Unlike other > platforms, ADL PCH does not have a counter for the time that the SLP_S0 > signal was asserted. Instead, firmware uses the aggregate of the Low Power > Mode (LPM) substate counters as the S0ix value. Since the LPM counters run > at a different frequency, this lead to misreporting of the S0ix time. > > Add a check for Alder Lake PCH and adjust the frequency accordingly when > display slp_s0_residency. > > Fixes: bbab31101f44 ("platform/x86/intel: pmc/core: Add Alderlake support to pmc core driver") > Signed-off-by: Rajvi Jingar <rajvi.jingar@linux.intel.com> > Signed-off-by: David E. Box <david.e.box@linux.intel.com> > --- > drivers/platform/x86/intel/pmc/core.c | 13 ++++++++++++- > 1 file changed, 12 insertions(+), 1 deletion(-) > > diff --git a/drivers/platform/x86/intel/pmc/core.c b/drivers/platform/x86/intel/pmc/core.c > index e489d2175e42..61ca7c37fb02 100644 > --- a/drivers/platform/x86/intel/pmc/core.c > +++ b/drivers/platform/x86/intel/pmc/core.c > @@ -66,7 +66,18 @@ static inline void pmc_core_reg_write(struct pmc_dev *pmcdev, int reg_offset, > > static inline u64 pmc_core_adjust_slp_s0_step(struct pmc_dev *pmcdev, u32 value) > { > - return (u64)value * pmcdev->map->slp_s0_res_counter_step; > + /* > + * ADL PCH does not have the SLP_S0 counter and LPM Residency counters are > + * used as a workaround which uses 30.5 usec tick. All other client > + * programs have the legacy SLP_S0 residency counter that is using the 122 > + * usec tick. > + */ > + const int lpm_adj_x2 = pmcdev->map->lpm_res_counter_step_x2; > + > + if (pmcdev->map == &adl_reg_map) > + return (u64)value * GET_X2_COUNTER((u64)lpm_adj_x2); > + else > + return (u64)value * pmcdev->map->slp_s0_res_counter_step; > } > > static int set_etr3(struct pmc_dev *pmcdev) > > base-commit: 02c464b73645404654359ad21f368a13735e2850 > -- > 2.34.1 >
On Mon, Mar 20, 2023 at 11:20 PM David E. Box <david.e.box@linux.intel.com> wrote: > > From: Rajvi Jingar <rajvi.jingar@linux.intel.com> > > For platforms with Alder Lake PCH (Alder Lake S and Raptor Lake S) the > slp_s0_residency attribute has been reporting the wrong value. Unlike other > platforms, ADL PCH does not have a counter for the time that the SLP_S0 > signal was asserted. Instead, firmware uses the aggregate of the Low Power > Mode (LPM) substate counters as the S0ix value. Since the LPM counters run > at a different frequency, this lead to misreporting of the S0ix time. > > Add a check for Alder Lake PCH and adjust the frequency accordingly when > display slp_s0_residency. OK! But one nit-pick below. Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> > Fixes: bbab31101f44 ("platform/x86/intel: pmc/core: Add Alderlake support to pmc core driver") > Signed-off-by: Rajvi Jingar <rajvi.jingar@linux.intel.com> > Signed-off-by: David E. Box <david.e.box@linux.intel.com> > --- > drivers/platform/x86/intel/pmc/core.c | 13 ++++++++++++- > 1 file changed, 12 insertions(+), 1 deletion(-) > > diff --git a/drivers/platform/x86/intel/pmc/core.c b/drivers/platform/x86/intel/pmc/core.c > index e489d2175e42..61ca7c37fb02 100644 > --- a/drivers/platform/x86/intel/pmc/core.c > +++ b/drivers/platform/x86/intel/pmc/core.c > @@ -66,7 +66,18 @@ static inline void pmc_core_reg_write(struct pmc_dev *pmcdev, int reg_offset, > > static inline u64 pmc_core_adjust_slp_s0_step(struct pmc_dev *pmcdev, u32 value) > { > - return (u64)value * pmcdev->map->slp_s0_res_counter_step; > + /* > + * ADL PCH does not have the SLP_S0 counter and LPM Residency counters are > + * used as a workaround which uses 30.5 usec tick. All other client microsecond or us or µs (I prefer the latter). > + * programs have the legacy SLP_S0 residency counter that is using the 122 > + * usec tick. microsecond or us or µs (I prefer the latter). > + */ > + const int lpm_adj_x2 = pmcdev->map->lpm_res_counter_step_x2; > + > + if (pmcdev->map == &adl_reg_map) > + return (u64)value * GET_X2_COUNTER((u64)lpm_adj_x2); > + else Redundant 'else'. > + return (u64)value * pmcdev->map->slp_s0_res_counter_step; > } > > static int set_etr3(struct pmc_dev *pmcdev) > > base-commit: 02c464b73645404654359ad21f368a13735e2850 > -- > 2.34.1 >
Hi, On 3/20/23 22:20, David E. Box wrote: > From: Rajvi Jingar <rajvi.jingar@linux.intel.com> > > For platforms with Alder Lake PCH (Alder Lake S and Raptor Lake S) the > slp_s0_residency attribute has been reporting the wrong value. Unlike other > platforms, ADL PCH does not have a counter for the time that the SLP_S0 > signal was asserted. Instead, firmware uses the aggregate of the Low Power > Mode (LPM) substate counters as the S0ix value. Since the LPM counters run > at a different frequency, this lead to misreporting of the S0ix time. > > Add a check for Alder Lake PCH and adjust the frequency accordingly when > display slp_s0_residency. > > Fixes: bbab31101f44 ("platform/x86/intel: pmc/core: Add Alderlake support to pmc core driver") > Signed-off-by: Rajvi Jingar <rajvi.jingar@linux.intel.com> > Signed-off-by: David E. Box <david.e.box@linux.intel.com> Thank you for your patch, I've applied this patch to my fixes branch: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=fixes Note it will show up in my fixes branch once I've pushed my local branch there, which might take a while. I will include this patch in my next fixes pull-req to Linus for the current kernel development cycle. Regards, Hans > --- > drivers/platform/x86/intel/pmc/core.c | 13 ++++++++++++- > 1 file changed, 12 insertions(+), 1 deletion(-) > > diff --git a/drivers/platform/x86/intel/pmc/core.c b/drivers/platform/x86/intel/pmc/core.c > index e489d2175e42..61ca7c37fb02 100644 > --- a/drivers/platform/x86/intel/pmc/core.c > +++ b/drivers/platform/x86/intel/pmc/core.c > @@ -66,7 +66,18 @@ static inline void pmc_core_reg_write(struct pmc_dev *pmcdev, int reg_offset, > > static inline u64 pmc_core_adjust_slp_s0_step(struct pmc_dev *pmcdev, u32 value) > { > - return (u64)value * pmcdev->map->slp_s0_res_counter_step; > + /* > + * ADL PCH does not have the SLP_S0 counter and LPM Residency counters are > + * used as a workaround which uses 30.5 usec tick. All other client > + * programs have the legacy SLP_S0 residency counter that is using the 122 > + * usec tick. > + */ > + const int lpm_adj_x2 = pmcdev->map->lpm_res_counter_step_x2; > + > + if (pmcdev->map == &adl_reg_map) > + return (u64)value * GET_X2_COUNTER((u64)lpm_adj_x2); > + else > + return (u64)value * pmcdev->map->slp_s0_res_counter_step; > } > > static int set_etr3(struct pmc_dev *pmcdev) > > base-commit: 02c464b73645404654359ad21f368a13735e2850
diff --git a/drivers/platform/x86/intel/pmc/core.c b/drivers/platform/x86/intel/pmc/core.c index e489d2175e42..61ca7c37fb02 100644 --- a/drivers/platform/x86/intel/pmc/core.c +++ b/drivers/platform/x86/intel/pmc/core.c @@ -66,7 +66,18 @@ static inline void pmc_core_reg_write(struct pmc_dev *pmcdev, int reg_offset, static inline u64 pmc_core_adjust_slp_s0_step(struct pmc_dev *pmcdev, u32 value) { - return (u64)value * pmcdev->map->slp_s0_res_counter_step; + /* + * ADL PCH does not have the SLP_S0 counter and LPM Residency counters are + * used as a workaround which uses 30.5 usec tick. All other client + * programs have the legacy SLP_S0 residency counter that is using the 122 + * usec tick. + */ + const int lpm_adj_x2 = pmcdev->map->lpm_res_counter_step_x2; + + if (pmcdev->map == &adl_reg_map) + return (u64)value * GET_X2_COUNTER((u64)lpm_adj_x2); + else + return (u64)value * pmcdev->map->slp_s0_res_counter_step; } static int set_etr3(struct pmc_dev *pmcdev)