From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@rjwysocki.net, len.brown@intel.com, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/4] cpufreq: Add configurable generic policies
Date: Mon, 07 Dec 2015 07:03:36 -0800 [thread overview]
Message-ID: <1449500616.4009.1.camel@linux.intel.com> (raw)
In-Reply-To: <20151207093320.GE3294@ubuntu>
On Mon, 2015-12-07 at 15:03 +0530, Viresh Kumar wrote:
> On 04-12-15, 16:08, Srinivas Pandruvada wrote:
> > diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> > index 177c768..8259c3c 100644
> > --- a/include/linux/cpufreq.h
> > +++ b/include/linux/cpufreq.h
> > @@ -76,6 +76,7 @@ struct cpufreq_policy {
> > unsigned int restore_freq; /* = policy->cur
> > before transition */
> > unsigned int suspend_freq; /* freq to set
> > during suspend */
> >
> > + u8 available_policies;
> Why don't we let the set-policy drivers fill in this field? No
> callback required then.
>
That is fine with me. In next revision I will add that.
Thanks,
Srinivas
next prev parent reply other threads:[~2015-12-07 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 0:08 [PATCH 0/4] cpufreq governors and Intel P state driver compatibility Srinivas Pandruvada
2015-12-05 0:08 ` [PATCH 1/4] cpufreq: Add configurable generic policies Srinivas Pandruvada
2015-12-07 9:33 ` Viresh Kumar
2015-12-07 15:03 ` Srinivas Pandruvada [this message]
2015-12-05 0:08 ` [PATCH 2/4] cpufreq: Add ondemand as a generic policy Srinivas Pandruvada
2015-12-07 9:34 ` Viresh Kumar
2015-12-05 0:08 ` [PATCH 3/4] cpufreq: intel_pstate: Change powersave to ondemand policy Srinivas Pandruvada
2015-12-05 0:08 ` [PATCH 4/4] cpufreq: intel_pstate: Add powersave policy support Srinivas Pandruvada
2015-12-08 14:35 ` [PATCH 0/4] cpufreq governors and Intel P state driver compatibility Thomas Renninger
2015-12-08 17:43 ` Srinivas Pandruvada
2015-12-09 15:02 ` Thomas Renninger
2015-12-09 16:12 ` Srinivas Pandruvada
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=1449500616.4009.1.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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).