A correction: On Tue, Jun 07, 2011 at 07:42:26AM +0200, Dominik Brodowski wrote: > > > Finally: > > > > > > > + policy->cur = data->freq_table[data->acpi_data->state].frequency; > > > > > > How do you know what state / frequency the CPU is running here? > > > > really the correct fix is for the upper level of cpufreq to > > simply no export this value at all, or to export the value > > that was last written. A driver should be free to decline > > to supply any current value. > > You didn't answer the question of how it is assured that policy->cur is > correctly initialized here. I just checked, and if it is initialized wrongly here, it doesn't matter much due to patch 4b31e774 . Best, Dominik -- 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
