On 24 March 2014 12:18, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > Ideally, .driver_data field of struct cpufreq_frequency_table must not be used > by core at all. But during a recent change if its value is same as > CPUFREQ_BOOST_FREQ macro, then it is treated specially by core. > > The value of this macro was set to ~2 earlier, i.e. 0xFFFFFFFD. In case some > driver is using this field for its own data and sets this field to -3, then with > two's complement that value will also become 0xFFFFFFFD. > > To fix this issue, lets change value of this flag to a very uncommon value which > shouldn't be used by any driver unless they want to use BOOST feature. > > Along with this update comments to make this more clear. > > Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx> > --- Please discard this patch now as I have sent a replacement patch. -- 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
