[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b324b5ad0609141117p5e67633o776871f80f2529c2@mail.gmail.com>
Date: Thu, 14 Sep 2006 11:17:40 -0700
From: "David Singleton" <daviado@...il.com>
To: "Auke Kok" <auke-jan.h.kok@...el.com>
Cc: "Greg KH" <greg@...ah.com>, linux-pm@...ts.osdl.org,
"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: OpPoint summary
On 9/14/06, Auke Kok <auke-jan.h.kok@...el.com> wrote:
> David Singleton wrote:
>
> > +static const struct cpu_id cpu_ids[] = {
> > + [CPU_BANIAS] = { 6, 9, 5 },
> > + [CPU_DOTHAN_A1] = { 6, 13, 1 },
> > + [CPU_DOTHAN_A2] = { 6, 13, 2 },
> > + [CPU_DOTHAN_B0] = { 6, 13, 6 },
> > + [CPU_MP4HT_D0] = {15, 3, 4 },
> > + [CPU_MP4HT_E0] = {15, 4, 1 },
> > +};
>
>
> Any reason why { 6, 13, 8 } is missing? My lenovo T43 identifies itself as such:
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 13
> model name : Intel(R) Pentium(R) M processor 1.86GHz
> stepping : 8
>
> I'm not sure a Dothan B1 exists, but some postings suggest even C0 and C1 are
> valid steppings. I'm sure OpPoint could work with those as well.
Yes it could. The centrino was the first platform I tested on and I used the
existing speedstep-centrino code from cpufreq. The 1.86Ghz was not in
the cpufreq base. But you can see how easy it is to add new operating points
for a new cpu.
Adding new platform support is quite straight forward. It basically requires
a function to transition to the new operating point and the parameters needed
for the transition.
David
>
> Auke
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists