From: viresh kumar <viresh.kumar@linaro.org>
To: Nishanth Menon <nm@ti.com>
Cc: Shawn Guo <shawn.guo@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"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>,
Carlos Hernandez <ceh@ti.com>
Subject: Re: [PATCH] cpufreq: cpufreq-cpu0: Use a sane boot frequency when booting with a mismatched bootloader configuration
Date: Wed, 20 Nov 2013 10:54:28 +0530 [thread overview]
Message-ID: <528C478C.1070901@linaro.org> (raw)
In-Reply-To: <528BA355.4040008@ti.com>
On Tuesday 19 November 2013 11:13 PM, Nishanth Menon wrote:
> we depend on the first transition to take us to a sane configuration -
> but we cannot predict when and if it will happen.
I really believe that it happens fairly quickly, isn't it? We straight away
start the sampling of load and withing few milliseconds we must be fixing the freq..
We aren't going to stay for the unknown, might be unstable, freq for ever..
next prev parent reply other threads:[~2013-11-20 5:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 2:22 [PATCH] cpufreq: cpufreq-cpu0: Use a sane boot frequency when booting with a mismatched bootloader configuration Nishanth Menon
2013-11-16 13:44 ` Shawn Guo
2013-11-17 4:02 ` Viresh Kumar
2013-11-18 14:45 ` Nishanth Menon
2013-11-18 15:57 ` Shawn Guo
2013-11-18 16:41 ` Nishanth Menon
2013-11-19 2:21 ` Shawn Guo
2013-11-19 3:46 ` Viresh Kumar
2013-11-19 14:16 ` Nishanth Menon
2013-11-19 14:26 ` Viresh Kumar
2013-11-19 14:59 ` Nishanth Menon
2013-11-19 15:32 ` Viresh Kumar
2013-11-19 15:48 ` Nishanth Menon
2013-11-19 17:10 ` Viresh Kumar
2013-11-19 17:43 ` Nishanth Menon
2013-11-20 5:24 ` viresh kumar [this message]
2013-11-20 14:59 ` Nishanth Menon
2013-11-21 7:41 ` Viresh Kumar
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=528C478C.1070901@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=ceh@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=shawn.guo@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).