8 Aug
2013
8 Aug
'13
2:33 a.m.
On 8 August 2013 04:55, Rafael J. Wysocki rjw@sisk.pl wrote:
It looks like it would require us to redefine .target() to take next_state instead of target_freq (at least in the acpi-cpufreq case), wouldn't it?
If we don't do it, then atleast for few drivers, like acpi-cpufreq, which use index more than just for frequency, we may end up calling cpufreq_frequency_table_target() twice. Once in the core and then in driver.
I believe this is doable and will post a patch soon.