On 28 November 2013 01:51, Rafael J. Wysocki <rjw@xxxxxxxxxxxxx> wrote: > I have a concern that on some systems you can't really say what frequency > you're running at the moment, however. Which ones? I know ACPI tries to play smart by handling the frequency stuff itself by marking CPUs not-related to each other for the kernel where they might actually be sharing clock line... But probably in these cases as well, atleast the cpufreq core should believe that it is running on a valid frequency even if actual hardware is running at something different.. Any other platforms you are aware of that implement ->target/target_index and where we can't say what freq are they running at? > So there should be a flag for > drivers indicating whether or not frequencies (or operation points in > general) are directly testable and the check should only be done for > the drivers with the flag set. Probably a flag with properties exactly opposite to what you mentioned, so that we don't need to modify most of the drivers.. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
