linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Len Brown <lenb@kernel.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] intel_idle: Add CPU model 74 (Atom Z34xx series)
Date: Fri, 17 Jun 2016 12:17:03 +0300	[thread overview]
Message-ID: <1466155023.30123.151.camel@linux.intel.com> (raw)
In-Reply-To: <CAJvTdKmDWQPtfHBtTEF2-_Ax=PvUpc6E56wR=6GjJcKf-kjXQw@mail.gmail.com>

On Wed, 2016-06-15 at 21:14 -0400, Len Brown wrote:
> Hi Andy,
> 
> Is this a patch from the Android kernel tree?

Nope. Though official Intel Yocto BSP containts almost same values for
this CPU, except for C1 (I decided no to take their since they also
provide different values for that state for BayTrail. And latter one is
in upstream). 

> Is there anybody testing the upstream kernel on this hardware?

I did. It works and I see changing values under sysfs. I'm not sure what
should I get from turbostat. Do I need to patch it as well to be able to
get something useful?

> 
> Past efforts to support old hardware that nobody tests upstream
> have resulted in all pain and no gain, and I'm not eager to
> repeat that experience.
> 
> thanks,
> -Len
> 
> 
> On Mon, Jun 6, 2016 at 1:06 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > Add CPU ID for Atom Z34xx processors. Datasheets indicate support
> > for this,
> > detailed information about potential quirks or limitations are
> > missing, though.
> > So we just reuse the definition for the previous ATOM series. The
> > quite similar
> > values (C1 is slightly deviated) are used in the official Intel
> > Edison BSP.
> > 
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> >  drivers/idle/intel_idle.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
> > index c966492..bb52275 100644
> > --- a/drivers/idle/intel_idle.c
> > +++ b/drivers/idle/intel_idle.c
> > @@ -1033,6 +1033,7 @@ static const struct x86_cpu_id
> > intel_idle_ids[] __initconst = {
> >         ICPU(0x2d, idle_cpu_snb),
> >         ICPU(0x36, idle_cpu_atom),
> >         ICPU(0x37, idle_cpu_byt),
> > +       ICPU(0x4a, idle_cpu_atom),
> >         ICPU(0x4c, idle_cpu_cht),
> >         ICPU(0x3a, idle_cpu_ivb),
> >         ICPU(0x3e, idle_cpu_ivt),
> > --
> > 2.8.1
> > 
> 
> 
> 

-- 

Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2016-06-17  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 17:06 [PATCH v1 1/1] intel_idle: Add CPU model 74 (Atom Z34xx series) Andy Shevchenko
2016-06-16  1:14 ` Len Brown
2016-06-17  9:17   ` 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=1466155023.30123.151.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-pm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).