Received: by 10.223.185.116 with SMTP id b49csp1093621wrg; Wed, 14 Feb 2018 11:31:09 -0800 (PST) X-Google-Smtp-Source: AH8x227Od9VjGVCxAnTtZJRb27cZD2MuEB9Y8mJxPmAGwby6u3kJ1uoULeJwoMru8mwuS7U6bxqN X-Received: by 10.99.97.81 with SMTP id v78mr70221pgb.243.1518636669872; Wed, 14 Feb 2018 11:31:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518636669; cv=none; d=google.com; s=arc-20160816; b=dlWJXEjeqX5tkEIT3j1tojDH3YbEeeT/29MslV2rgjfispMzf3KBTgN0e6Lw5mwpGR B/Yo9sDK2JZA2oRXI2j9aa5WQUX7ZeozChjnUcWTmNvrxMDQ8HJy2QSRubeNPtb9oyvn CLn5XiHiSRwM030rPTH+00sSN5NRCc4YPqd/+F9gfoqOj1T99tZbqxV9OpDMHSlLdC33 Q+4FBzdhe+LaJVe87015kgq2jzBCnUoX0Nww0Ke12om0dfGiBgcowB44XugfcAsx8Oqb TZUOkpBp3GGOA1V90si6vEIRePZPhQ69bmXZ9dovh3E+hWVgYGTpmhzDzUI82Nei3NEZ nefA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=i84MgGY3Rv1PR8xcnFsbV3sOKtZYCPvfiLyofY2ihig=; b=nncXxcWe+UOnmUCowfFigc4sKlOGzF77eZJFbnLgGnYRWqFlKNC4LRuwE4elo/RjCY ORhZ0eOJl4hKf7IYdR/2bbFVOFMvDJFfygryl/OOVEU43A1BPmJ75SRdLTFSspZZpNba Xr57xDjNu5UkaoIzva7uunP1e6LuWTuKQOMo0A+/8pJm2h/kVIK+noW+e6N4hE1CPQKY V0cXsNLx7HUsdai/+ifa6u4+W2xysO8mzQPoUMg3SEiPNow5rmcfe7t+23in161mwZK3 suhWgm8GUFAQq8HYtsFkPfwz5ms2FFC9lvl7Y56zMc2aSJFNcKubiPV0QHSHP++aAQEV /X/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p25si78203pfh.197.2018.02.14.11.30.55; Wed, 14 Feb 2018 11:31:09 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1163011AbeBNT3v (ORCPT + 99 others); Wed, 14 Feb 2018 14:29:51 -0500 Received: from mga12.intel.com ([192.55.52.136]:32591 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1162999AbeBNT3t (ORCPT ); Wed, 14 Feb 2018 14:29:49 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Feb 2018 11:29:49 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,513,1511856000"; d="scan'208";a="20058356" Received: from avandeve-mobl.amr.corp.intel.com (HELO [10.24.10.62]) ([10.24.10.62]) by fmsmga002.fm.intel.com with ESMTP; 14 Feb 2018 11:29:48 -0800 Subject: Re: [PATCH] platform/x86: intel_turbo_max_3: Remove restriction for HWP platforms To: Andy Shevchenko , Srinivas Pandruvada Cc: Darren Hart , Andy Shevchenko , Platform Driver , Linux Kernel Mailing List References: <20180212195047.23671-1-srinivas.pandruvada@linux.intel.com> From: Arjan van de Ven Message-ID: <7791d2f2-3a74-6dee-7055-feeaa6bbe2d8@linux.intel.com> Date: Wed, 14 Feb 2018 11:29:48 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/14/2018 11:29 AM, Andy Shevchenko wrote: > On Mon, Feb 12, 2018 at 9:50 PM, Srinivas Pandruvada > wrote: >> On systems supporting HWP (Hardware P-States) mode, we expected to >> enumerate core priority via ACPI-CPPC tables. Unfortunately deployment of >> TURBO 3.0 didn't use this method to show core priority. So users are not >> able to utilize this feature in HWP mode. >> >> So remove the loading restriction of this driver for HWP enabled systems. >> Even if there are some systems, which are providing the core priority via >> ACPI CPPC, this shouldn't cause any conflict as the source of priority >> definition is same. >> > > Pushed to my review and testing queue, thanks! > > P.S. Should it go to stable? older stable at least did not have the problem