On 24 March 2014 13:51, Lukasz Majewski <l.majewski@xxxxxxxxxxx> wrote: > I think that a name of the patchset, for which the current setting > causes problem would be welcome here. I couldn't find a lkml link to the exact message earlier, but it was discussed here: https://patchwork.kernel.org/patch/3865481/ > Otherwise, I can only ask why it is not possible to add > #define SPECIAL_SETTING ~3 ? Driver wants to use this field for +ve and -ve values and it should be free to do so.... And ~2 was creating problems when he used -3 for this field.. If we make it ~3, then he will face problem for -4.. So, I used a special value 0xABABABAB here whose integer value is: -1414812757 The only other option we have is to add another field "bool boost" in cpufreq_frequency_table, which is the last thing I wanted to do. And that's the point Gautham was trying to make in one of our IRC chats as well.. -- 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
