From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Lan Tianyu <lantianyu1986@gmail.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>
Subject: Re: [Query] CPUFreq: Why do we need policy->user_policy?
Date: Tue, 27 Aug 2013 23:20:32 +0200 [thread overview]
Message-ID: <1734682.b8u1f0b3XY@vostro.rjw.lan> (raw)
In-Reply-To: <CAOLK0pztfCd9ov297t0CW0C5S2iOSb9FJFHq9ycqwYGRiyifmA@mail.gmail.com>
On Tuesday, August 27, 2013 10:04:52 PM Lan Tianyu wrote:
> 2013/8/27 Viresh Kumar <viresh.kumar@linaro.org>:
> > On 26 August 2013 20:53, Lan Tianyu <lantianyu1986@gmail.com> wrote:
> >> So far as I know, it stores some user's config and cpufreq_update_policy()
> >> bases on the data in the struct to start a new policy. Cpu thermal driver
> >> (/driver/thermal/cpu_cooling.c)also will its value to update freq policy
> >> when receive a cpufreq policy adjust notification.
> >
> > Yeah, but how are these different from policy->min/max/policy/governor?
> > Why do we need to replicate this information?
>
> From my understanding.policy->min/max may be modified by some drivers
> but the user_policy only store user space config and should not be changed
> by other reason. :)
Yes, that was the original idea IIRC, so separate user settings from stuff that
may be changed internally by the kernel.
Thanks,
Rafael
next prev parent reply other threads:[~2013-08-27 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 14:30 Viresh Kumar
2013-08-26 14:48 ` Rafael J. Wysocki
2013-08-26 15:23 ` Lan Tianyu
2013-08-27 10:59 ` Viresh Kumar
2013-08-27 14:04 ` Lan Tianyu
2013-08-27 21:20 ` Rafael J. Wysocki [this message]
2013-08-28 5:42 ` 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=1734682.b8u1f0b3XY@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=lantianyu1986@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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
all inboxes | Powered by JetHome®