public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] x86: TunnelCreek: switch P state to the highest freq
Date: Wed, 6 Mar 2019 13:09:51 +0200	[thread overview]
Message-ID: <20190306110951.GA9224@smile.fi.intel.com> (raw)
In-Reply-To: <CAEUhbmXDc=6Ko02HTXx4xx5H9p1XFvNo9Ko=WzQr2tfqppn5GQ@mail.gmail.com>

On Thu, Feb 28, 2019 at 11:29:50AM +0800, Bin Meng wrote:
> On Thu, May 24, 2018 at 12:00 PM Bin Meng <bmeng.cn@gmail.com> wrote:
> > On Thu, Apr 12, 2018 at 4:07 PM, Christian Gmeiner
> > <christian.gmeiner@gmail.com> wrote:

> So to me this seems to match my understanding about EIST. If this is
> true, then I can't explain why Christian's patch is needed since the
> EIST is disabled on TunnelCreek by default and the processor should
> already run at the highest performance.

The some internal documents I found suggesting that first what one needs to do
is to be sure that EIST is enabled / disabled by reading a bit from CPUID.

(There is no mention of the exact bit, I'm guessing it might be X86_FEATURE_EST)

It also refers to IA32_MISC_ENABLE MSR, i.e. bit 20
(MSR_IA32_MISC_ENABLE_SPEEDSTEP_LOCK_BIT) and bit 16
(MSR_IA32_MISC_ENABLE_ENHANCED_SPEEDSTEP_BIT), that firmware can set up
accordingly.

Hope this helps.

P.S. All names are implying Linux kernel source code.

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2019-03-06 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12  8:07 [U-Boot] [PATCH v2 1/2] x86: TunnelCreek: switch P state to the highest freq Christian Gmeiner
2018-04-12  8:07 ` [U-Boot] [PATCH v2 2/2] x86: Intel Crown Bay board: switch to TunnelCreek cpu driver Christian Gmeiner
2018-05-24  4:00 ` [U-Boot] [PATCH v2 1/2] x86: TunnelCreek: switch P state to the highest freq Bin Meng
2019-02-28  3:29   ` Bin Meng
2019-03-06 11:09     ` Andy Shevchenko [this message]
2019-03-11 14:41       ` Bin Meng
2019-03-13  9:27         ` Christian Gmeiner
2019-03-15  8:03           ` Bin Meng
2019-04-01  7:48             ` Christian Gmeiner
2019-04-01  8:08               ` Bin Meng
2019-04-04 12:54                 ` Andy Shevchenko

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=20190306110951.GA9224@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox