From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Lists linaro-kernel <linaro-kernel@lists.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>,
Pierre Ossman <pierre-list@ossman.eu>
Subject: Re: [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy()
Date: Mon, 10 Mar 2014 13:37:45 +0800 [thread overview]
Message-ID: <CAKohponVBFaZY2tE8kJ91Gtj9MdvFKzGgWPNWxi38Kg8q9YUug@mail.gmail.com> (raw)
In-Reply-To: <CAKohpokKJUt4UhC5_dJAhU3LCBwht4pfDWT5Lqo0T1-y_M31=A@mail.gmail.com>
On 26 February 2014 13:15, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 26 February 2014 03:59, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
>> Yes, what exactly do we need it for in the core?
>
> Its probably there to make things faster. We cache the value so that we
> don't go to the hardware to read/calculate that again. Isn't it?
>
> And we need to know current freq on many occasions. One of that is that
> many drivers need to know the relation between current and new freq before
> they can make the change. As they might need to play with volt regulators
> before or after the freq change. Also it is used mainly in our loops_per_jiffiy
> calculations.
Ping!!
prev parent reply other threads:[~2014-03-10 5:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 11:00 [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy() Viresh Kumar
2014-02-14 11:00 ` [PATCH 2/2] cpufreq: don't call cpufreq_update_policy() on CPU addition Viresh Kumar
2014-02-17 0:21 ` Rafael J. Wysocki
2014-02-17 5:15 ` Viresh Kumar
2014-02-17 22:22 ` Rafael J. Wysocki
2014-02-17 8:43 ` Srivatsa S. Bhat
2014-02-17 8:54 ` Viresh Kumar
2014-02-17 8:59 ` Srivatsa S. Bhat
2014-02-17 0:28 ` [PATCH 1/2] cpufreq: Return error if ->get() failed in cpufreq_update_policy() Rafael J. Wysocki
2014-02-17 5:14 ` Viresh Kumar
2014-02-17 8:19 ` Srivatsa S. Bhat
2014-02-17 8:39 ` Viresh Kumar
2014-02-17 8:55 ` Srivatsa S. Bhat
2014-02-17 9:10 ` Viresh Kumar
2014-02-17 22:00 ` Rafael J. Wysocki
2014-02-18 2:19 ` Viresh Kumar
2014-02-25 4:41 ` Viresh Kumar
2014-02-25 5:53 ` Srivatsa S. Bhat
2014-02-25 6:08 ` Viresh Kumar
2014-02-25 13:10 ` Rafael J. Wysocki
2014-02-25 14:42 ` Viresh Kumar
2014-02-25 22:29 ` Rafael J. Wysocki
2014-02-26 5:15 ` Viresh Kumar
2014-03-10 5:37 ` Viresh Kumar [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=CAKohponVBFaZY2tE8kJ91Gtj9MdvFKzGgWPNWxi38Kg8q9YUug@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pierre-list@ossman.eu \
--cc=rjw@rjwysocki.net \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).