On Mon, 7 Feb 2011 19:13:21 +0000
Matthew Garrett <mjg59@xxxxxxxxxxxxx> wrote:
> On Fri, Feb 04, 2011 at 09:11:56AM -0800, Jesse Barnes wrote:
> > > +++ linux/drivers/platform/x86/intel_ips.c 2011-02-04 15:25:40.205627688 +0100
> > > @@ -1399,6 +1399,10 @@
> > > limits = &ips_lv_limits;
> > > else if (strstr(boot_cpu_data.x86_model_id, "CPU U"))
> > > limits = &ips_ulv_limits;
> > > + else if (strstr(boot_cpu_data.x86_model_id, "CPU 610"))
> > > + limits = &ips_sv_limits;
> > > + else if (strstr(boot_cpu_data.x86_model_id, "CPU 520"))
> > > + limits = &ips_sv_limits;
> > > else {
> > > dev_info(&ips->dev->dev, "No CPUID match found.\n");
> > > goto out;
> >
> > Yep, that's fine with me, thanks for the patch!
>
> Are these the only two embedded Arrandales? Is there really no MSR that
> gives you the voltage range?
AFAIK this is the same method the Windows driver uses, so I don't think
so.
Fortunately the on-die integration in Sandy Bridge makes all this
unnecessary, so I don't expect you'll have to continually add entries
to this list over time.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
