From patchwork Fri Mar 22 22:45:18 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: srinivas pandruvada X-Patchwork-Id: 10866601 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 2E6E515AC for ; Fri, 22 Mar 2019 22:45:42 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 1F44F2A9F9 for ; Fri, 22 Mar 2019 22:45:42 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 0F0312AA05; Fri, 22 Mar 2019 22:45:42 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=unavailable version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id B39932AA06 for ; Fri, 22 Mar 2019 22:45:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728196AbfCVWp2 (ORCPT ); Fri, 22 Mar 2019 18:45:28 -0400 Received: from mga18.intel.com ([134.134.136.126]:15693 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728423AbfCVWp2 (ORCPT ); Fri, 22 Mar 2019 18:45:28 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2019 15:45:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,256,1549958400"; d="scan'208";a="309622827" Received: from spandruv-mobl.amr.corp.intel.com ([10.254.53.177]) by orsmga005.jf.intel.com with ESMTP; 22 Mar 2019 15:45:25 -0700 From: Srinivas Pandruvada To: rjw@rjwysocki.net, lenb@kernel.org, viresh.kumar@linaro.org Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, pprakash@codeaurora.org, wangxiongfeng2@huawei.com, Srinivas Pandruvada Subject: [PATCH 0/2] Correct the processing for base_frequency Date: Fri, 22 Mar 2019 15:45:18 -0700 Message-Id: <20190322224520.6740-1-srinivas.pandruvada@linux.intel.com> X-Mailer: git-send-email 2.17.2 Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP The base_frequency display in cpufreq sysfs for intel_pstate gets the guaranteed ratio by reading CPPC guaranteed performance register as a first preference before falling back to x86 MSR for Hardware P-state Capabilities. The current code in cppc_acpi.c assumed that "guaranteed performance register" can be an integer field, which is invalid as per ACPI spec. So this change explicitly check for INTEGER values for invalid BIOS/firmware and ignore. Also guaranteed performance register field is optional and when not present, nominal performance can be used as the guaranteed performance. But spec calls that this is true only in non-autonomous mode. So no change is made in cppc_acpi.c to make nominal as guaranteed in this case to avoid dependency on autonomous and non-autonomous mode. Instead a change is added to intel_pstate driver, which is specific to x86 to make nominal as guaranteed when guaranteed performance field is absent or has invalid value. Also we are working to clarify this non-autonomous mode requirement through ACPI standard body. Srinivas Pandruvada (2): ACPI / CPPC: Fix processing for guaranteed performance cpufreq: intel_pstate: Also use cppc nominal_perf for base_frequency drivers/acpi/cppc_acpi.c | 10 ++++++++-- drivers/cpufreq/intel_pstate.c | 3 +++ 2 files changed, 11 insertions(+), 2 deletions(-)