All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: intel_turbo_max_3: Remove restriction for HWP platforms
Date: Wed, 14 Feb 2018 11:29:48 -0800	[thread overview]
Message-ID: <7791d2f2-3a74-6dee-7055-feeaa6bbe2d8@linux.intel.com> (raw)
In-Reply-To: <CAHp75VdUnw0NjcNDKzFp-hZWho4A8RV=9Xthz-foZ6wTaT+Ftg@mail.gmail.com>

On 2/14/2018 11:29 AM, Andy Shevchenko wrote:
> On Mon, Feb 12, 2018 at 9:50 PM, Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> 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

  reply	other threads:[~2018-02-14 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 19:50 [PATCH] platform/x86: intel_turbo_max_3: Remove restriction for HWP platforms Srinivas Pandruvada
2018-02-14 19:29 ` Andy Shevchenko
2018-02-14 19:29   ` Arjan van de Ven [this message]
2018-02-14 23:47   ` Srinivas Pandruvada

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7791d2f2-3a74-6dee-7055-feeaa6bbe2d8@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.