Matthew Locke <matt at nomadgs.com> wrote on 07/26/2006 09:44:52 AM: > btw, we are in complete agreement about using named points. This first > set of patches is meant to introduce the operating point concept into > the kernel without requiring massive changes to cpufreq. This layer > extends the bottom part of cpufreq to enable the control of multiple > parameters beyond just cpu frequency and voltage across architectures. > Currently, cpufreq does not use named operating points so we need to > make sure cpufreq can use the power op API and continue to function. > This topic also ties into our other email discussion on creating op > points and names are assigned to op points. Hi, Maybe I missed those discussions about extending cpufreq with other attributes. On what list has it been posted ? I am working on a throttling module and would like to implement it as a cpufreq driver. Also closer integration of the on-demand governor and the cpu scheduler (and hopefully thermal control) would be nice. This governor uses aged information to control cpus, whereas the scheduler knows the future. Thermal control could hint the scheduler, before a cpu gets too hot and throttled down. Are there any ideas floating around ?
