Received: by 10.223.185.116 with SMTP id b49csp1343727wrg; Wed, 14 Feb 2018 15:48:47 -0800 (PST) X-Google-Smtp-Source: AH8x225CzUowlT286E8KBaPxNCKJ2zviVSGxFaxesd+lLGiu4dKDZkRUZK68q/iR2MQmqW/Sb5VC X-Received: by 10.99.125.74 with SMTP id m10mr602242pgn.354.1518652127557; Wed, 14 Feb 2018 15:48:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518652127; cv=none; d=google.com; s=arc-20160816; b=zFAqwl92u7Y0VkHoVx9FDT+IwOaI/M0zVIAvaLMBT63FvGft60F1HYHf8vUi6+7q69 ptY2ZVK/K0/k3AWFr3kHG5NgIjUhpe17FYdpDIlWhrztCNoo3Ne+Ea5RHEtTOOpeYKjC uWnAmCIy+2oOba8eaagqZLX9YlMRCE8Y96fLTqwo6HMi5U0hAnCrE+lu72K9jN/S1MpJ LZU09svhwwXjq3FWNOILdxSzQKsda++RPti/EfGb57YNaDohSJ0s91VmOQogjpMq/cnA BMLHWrXX3p3vS5asjKlKIrwFA9qerfpkp3U1WCups8RP4+RieER15dZHbGBsTDZYhmBL rh5w== 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:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=abrCiPZIUCbdi7SbvevosJMTwBmcSPPtHmLtlPQUPMA=; b=SUDjgsn/3QI3J8ttuA191WSVqpuB+Lc58UvBZQ4LwKfhoTNzR8Mt4v2XHvpPytVThT Lkhoune6DrUAwxRae+c22NodPP1I3C06CnAqNBIzAdg0YR7U5tt5icQ59UA8i3jUqsx6 J3IM6V6ESB+7NrzIo8WzhJhwA3D3S9DYPXaFEHAUck/5kj8whVU26qc6GcjPOFwhzP6O aN+hSxWPBsAvylMnz6PfeSOz5dkhgUFF7MC1nQ+GDuv5bOTWNV1LfHif47AZ+OiDNoqu 5lF+FlGTslGmIxBgtFZvwCPkExq7+3Ii+uF+IYOVVzCAE9rr/KPafNs9rE4ClW1KJbI2 X/2g== 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 u12-v6si156976pls.285.2018.02.14.15.48.32; Wed, 14 Feb 2018 15:48:47 -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 S1032134AbeBNXrw (ORCPT + 99 others); Wed, 14 Feb 2018 18:47:52 -0500 Received: from mga14.intel.com ([192.55.52.115]:1073 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031901AbeBNXru (ORCPT ); Wed, 14 Feb 2018 18:47:50 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Feb 2018 15:47:50 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,515,1511856000"; d="scan'208";a="27995167" Received: from spandruv-mobl.ch.intel.com ([10.34.228.212]) by orsmga003.jf.intel.com with ESMTP; 14 Feb 2018 15:47:49 -0800 Message-ID: <1518652069.3239.4.camel@linux.intel.com> Subject: Re: [PATCH] platform/x86: intel_turbo_max_3: Remove restriction for HWP platforms From: Srinivas Pandruvada To: Andy Shevchenko Cc: Darren Hart , Andy Shevchenko , Platform Driver , Linux Kernel Mailing List , arjan@linux.intel.com Date: Wed, 14 Feb 2018 15:47:49 -0800 In-Reply-To: References: <20180212195047.23671-1-srinivas.pandruvada@linux.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 (3.22.6-2.fc25) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2018-02-14 at 21:29 +0200, 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? I want to avoid stable kernel for now. Thanks, Srinivas > > > Signed-off-by: Srinivas Pandruvada > .com> > > Reported-and-tested-and-reviewed-by: Arjan van de Ven > intel.com> > > --- > >  drivers/platform/x86/intel_turbo_max_3.c | 3 --- > >  1 file changed, 3 deletions(-) > > > > diff --git a/drivers/platform/x86/intel_turbo_max_3.c > > b/drivers/platform/x86/intel_turbo_max_3.c > > index d4ea01805879..a6d5aa0c3c47 100644 > > --- a/drivers/platform/x86/intel_turbo_max_3.c > > +++ b/drivers/platform/x86/intel_turbo_max_3.c > > @@ -138,9 +138,6 @@ static int __init itmt_legacy_init(void) > >         if (!id) > >                 return -ENODEV; > > > > -       if (boot_cpu_has(X86_FEATURE_HWP)) > > -               return -ENODEV; > > - > >         ret = cpuhp_setup_state(CPUHP_AP_ONLINE_DYN, > >                                 "platform/x86/turbo_max_3:online", > >                                 itmt_legacy_cpu_online, NULL); > > -- > > 2.13.6 > > > > >