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: Thu, 4 Apr 2019 15:54:00 +0300 [thread overview]
Message-ID: <20190404125400.GU9224@smile.fi.intel.com> (raw)
In-Reply-To: <CAEUhbmVfGzbro9CQnndmooZK9AqGLHTeQ+Sf-qoWvVNifn9KDw@mail.gmail.com>
On Mon, Apr 01, 2019 at 04:08:33PM +0800, Bin Meng wrote:
> On Mon, Apr 1, 2019 at 3:48 PM Christian Gmeiner
> <christian.gmeiner@gmail.com> wrote:
> > Am Fr., 15. März 2019 um 09:03 Uhr schrieb Bin Meng <bmeng.cn@gmail.com>:
> > > On Wed, Mar 13, 2019 at 5:27 PM Christian Gmeiner
> > > <christian.gmeiner@gmail.com> wrote:
> > > > Am Mo., 11. März 2019 um 15:41 Uhr schrieb Bin Meng <bmeng.cn@gmail.com>:
> > > > > On Wed, Mar 6, 2019 at 7:09 PM Andy Shevchenko
> > > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > > > 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:
> > > > We need to set these two msr registers to the values they provided to us.
> > > > These msr register should be described in #29324.
> > >
> > > Could you please provide details about these 2 MSR registers? And is
> > > there any official document from Intel about what is the behavior of
> > > having EIST disabled?
> > >
> >
> > I only got an excerpt of two pages describing these 2 MSR and I am quite sure
> > I am not allowed to share these. As I wrote these MSR should be documented
> > in #29324 (which I do not have access to).
> >
>
> Thanks for sharing the information.
>
> Andy, do you have access to the #29324, and check whether it has some
> explanation about my assumption about Intel EIST?
I have no idea what that number means.
Christian might sent me (*) at least a title of the document for easy search.
*) privately to @intel.com address, for example.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2019-04-04 12:54 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
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 [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=20190404125400.GU9224@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