From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Patch Tracking <patches@linaro.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nishanth Menon <nm@ti.com>, Carlos Hernandez <ceh@ti.com>
Subject: Re: [PATCH V2] cpufreq: Make sure CPU is running on a freq from freq-table
Date: Thu, 28 Nov 2013 21:31:53 +0100 [thread overview]
Message-ID: <1591147.c0NqbMglPZ@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpomDu0Xh8Q1PEo3n+JwE26GkJTxhdezGPs7aJwJXjaTvLQ@mail.gmail.com>
On Thursday, November 28, 2013 07:44:02 PM Viresh Kumar wrote:
> On 28 November 2013 19:42, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > On Thursday, November 28, 2013 07:11:17 PM Viresh Kumar wrote:
> >> Okay.. So wouldn't it be better that we add this special flag only when we
> >> face a real problem? Otherwise this flag might stay unused for long time
> >> and then we might end up removing it..
>
> What about this one?
Well, so are you saying that the problem is only theoretical now?
> > SKIP_INITIAL_FREQUENCY_CHECK ?
>
> Looks fine.. In case this is required, you want this to be set initially for any
> driver?
That depends on what is less work and code churn. How many platforms/drivers
have this problem today? Which ones are they?
Rafael
prev parent reply other threads:[~2013-11-28 20:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 4:23 [PATCH V2] cpufreq: Make sure CPU is running on a freq from freq-table Viresh Kumar
2013-11-25 16:38 ` Dirk Brandewie
2013-11-25 17:01 ` Viresh Kumar
2013-11-25 17:43 ` Dirk Brandewie
2013-11-25 21:13 ` Rafael J. Wysocki
2013-11-26 2:01 ` Viresh Kumar
2013-11-26 6:14 ` viresh kumar
2013-11-26 20:21 ` Rafael J. Wysocki
2013-11-27 3:01 ` Viresh Kumar
2013-11-27 14:22 ` Rafael J. Wysocki
2013-11-27 15:52 ` Viresh Kumar
2013-11-27 20:21 ` Rafael J. Wysocki
2013-11-28 3:20 ` Viresh Kumar
2013-11-28 13:09 ` Rafael J. Wysocki
2013-11-28 13:41 ` Viresh Kumar
2013-11-28 14:12 ` Rafael J. Wysocki
2013-11-28 14:14 ` Viresh Kumar
2013-11-28 20:31 ` Rafael J. Wysocki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1591147.c0NqbMglPZ@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=ceh@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=dirk.brandewie@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=patches@linaro.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).