All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform: x86: Support Turbo Boost Max for non HWP systems
Date: Wed, 18 Jan 2017 08:31:54 -0800	[thread overview]
Message-ID: <1484757114.4497.124.camel@linux.intel.com> (raw)
In-Reply-To: <CAHp75Vdcyv9JpZ6Mj_JiftS9r2tQc-Vno05uFpBfQOanGkkY_g@mail.gmail.com>

On Wed, 2017-01-18 at 05:24 +0200, Andy Shevchenko wrote:
> On Wed, Jan 18, 2017 at 2:39 AM, Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> > 
> > On Tue, 2017-01-17 at 16:32 -0800, Darren Hart wrote:
> > > 
> > > On Wed, Jan 11, 2017 at 12:36:34PM -0800, Srinivas Pandruvada
> > > wrote:
> 
> > 
> > > 
> > > intel_bdw_turbo.c
> > > CONFIG_INTEL_BDW_TURBO
> > We should add _MAX_3 as this is a technology more than simple
> > TURBO.
> > 
> > CONFIG_INTEL_BDW_TURBO_MAX_3
> 
> Would it be re-used in the future?
> I would suggest INTEL_TURBO_MAX_3
Current direction is to have ACPI CPPC. I am fine dropping BDW.
Let me resubmit patch. Anyway my script missed sending emails to all in
the maintainer list, so have to resend.

Thanks,
Srinivas

      reply	other threads:[~2017-01-18 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 20:36 [PATCH] platform: x86: Support Turbo Boost Max for non HWP systems Srinivas Pandruvada
2017-01-18  0:32 ` Darren Hart
2017-01-18  0:39   ` Srinivas Pandruvada
2017-01-18  3:24     ` Andy Shevchenko
2017-01-18 16:31       ` Srinivas Pandruvada [this message]

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=1484757114.4497.124.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.