[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpom95rVO4AP6spzHWp3Oy6Lxmm3OnJte6d-E+vrdDQ2UUg@mail.gmail.com>
Date: Mon, 24 Mar 2014 14:03:20 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Lukasz Majewski <l.majewski@...sung.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
"ego@...ux.vnet.ibm.com" <ego@...ux.vnet.ibm.com>,
Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>
Subject: Re: [PATCH] cpufreq: set value of CPUFREQ_BOOST_FREQ to 0xABABABAB
On 24 March 2014 13:51, Lukasz Majewski <l.majewski@...sung.com> 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 linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists