From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Dirk Brandewie <dirk.j.brandewie@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: intel_pstate: Add CPU ID for Braswell processor
Date: Thu, 28 Aug 2014 01:48:42 +0200 [thread overview]
Message-ID: <1489037.zFJ48ZYqaQ@vostro.rjw.lan> (raw)
In-Reply-To: <53FE0BB1.9060201@gmail.com>
On Wednesday, August 27, 2014 09:47:45 AM Dirk Brandewie wrote:
> On 08/22/2014 03:19 AM, Viresh Kumar wrote:
> > On 22 August 2014 15:35, Mika Westerberg
> > <mika.westerberg@linux.intel.com> wrote:
> >> This is pretty much the same as Intel Baytrail, only the CPU ID is
> >> different. Add the new ID to the supported CPU list.
> >>
> >> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> >> Cc: Dirk Brandewie <dirk.j.brandewie@intel.com>
> >
> > Dirk might be away on holidays..
>
> Yes Sorry
>
> Acked-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
Queued up for 3.17-rc3, thanks!
>
> >
> >> ---
> >> drivers/cpufreq/intel_pstate.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> >> index c5eac949760d..a3cf8994160b 100644
> >> --- a/drivers/cpufreq/intel_pstate.c
> >> +++ b/drivers/cpufreq/intel_pstate.c
> >> @@ -660,6 +660,7 @@ static const struct x86_cpu_id intel_pstate_cpu_ids[] = {
> >> ICPU(0x3f, core_params),
> >> ICPU(0x45, core_params),
> >> ICPU(0x46, core_params),
> >> + ICPU(0x4c, byt_params),
> >> ICPU(0x4f, core_params),
> >> ICPU(0x56, core_params),
> >> {}
> >
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2014-08-27 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 10:05 Mika Westerberg
2014-08-22 10:19 ` Viresh Kumar
2014-08-27 16:47 ` Dirk Brandewie
2014-08-27 23:48 ` Rafael J. Wysocki [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=1489037.zFJ48ZYqaQ@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®