Messages in this thread | | | Date | Sun, 14 Mar 2004 17:33:10 +0100 | From | Dominik Brodowski <> | Subject | Re: powernow-k8 updates |
| |
On Wed, Mar 10, 2004 at 02:48:11PM +0100, Bruno Ducrot wrote: > ducrot@poupon:~/kernel/linux-2.6.4-bk-acpi> grep EXPORT drivers/acpi/processor.c > EXPORT_SYMBOL(acpi_processor_register_performance); > EXPORT_SYMBOL(acpi_processor_unregister_performance); > EXPORT_SYMBOL(acpi_processor_set_thermal_limit); > > So all you need are acpi_processor_register_performance() and > acpi_processor_unregister_performance(). I'm pretty sure that those > functions are in 2.6.4-rc2.
These functions are indeed in 2.6.3 and 2.6.4 -- and they work fine. If you have any questions related to them, please ask me.
> If you want to play with those functions, you have to include > <acpi/processor.h>, and then you have to register a driver via: > acpi_processor_register_performance(&pr, cpu) where: > - cpu is the cpu id (point-of-view of Linux, not the acpi cpu id), > - pr is a struct acpi_processor_performance (defined in > acpi/processor.h). > > You will have then for free: > - configurations via the acpi_processor_performance structure, > - handling of the _PPC object, so that you don't have to care about > changes for that in the driver. That will be done via classic > ACPI event notifications to the processor, via the limit interface > writen in drivers/acpi/processor.c, and cpufreq notion of notifiers.
Minor correction: only the first and last steps are indeed used to handle _PPC, IIRC.
Also, you'll have - support for _PDC, if needed - proper embedding into ACPI core - the /proc/acpi/processor/./performance interface which some still tend to like...
Dominik [unhandled content-type:application/pgp-signature] | |