From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@rjwysocki.net, morten.rasmussen@arm.com, Juri.Lelli@arm.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] cpufreq: intel_pstate: Support of energy performance hint using HWP
Date: Thu, 17 Nov 2016 11:31:32 -0800 [thread overview]
Message-ID: <1479411092.6544.129.camel@linux.intel.com> (raw)
In-Reply-To: <20161117064954.GD4894@vireshk-i7>
Hi Viresh,
On Thu, 2016-11-17 at 12:19 +0530, Viresh Kumar wrote:
> Hi Srinivas,
>
> I don't think other platforms need it for now and so it is fine to
> add these to the driver itself.
Good to know. In this case I will proceed with change only local to
intel_pstate.
>
> On 15-11-16, 14:59, Srinivas Pandruvada wrote:
> >
> > +static ssize_t show_energy_performance_available_preferences(
>
> Maybe a personal preference, but I would have broken the line after
> ssize_t instead of where you have done it.
I can change that.
>
> >
> > + struct cpufreq_policy *policy,
> > char *buf)
> > +{
> > +static struct freq_attr *hwp_cpufreq_attrs[] = {
> > + &energy_performance_preference,
> > + &energy_performance_available_preferences,
> > + NULL,
> > +};
>
> What about adding these to intel_pstate_attr_group instead ?
Sure.
Thanks,
Srinivas
prev parent reply other threads:[~2016-11-17 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 22:59 [RFC][PATCH] cpufreq: Support of Energy Performance preference Srinivas Pandruvada
2016-11-15 22:59 ` [RFC][PATCH] cpufreq: intel_pstate: Support of energy performance hint using HWP Srinivas Pandruvada
2016-11-17 6:49 ` Viresh Kumar
2016-11-17 19:31 ` Srinivas Pandruvada [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=1479411092.6544.129.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=Juri.Lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=morten.rasmussen@arm.com \
--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).