From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Robert Moore <robert.moore@intel.com>,
"Schmauss, Erik" <erik.schmauss@intel.com>,
Juri Lelli <juri.lelli@redhat.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
devel@acpica.org, Prashanth Prakash <pprakash@codeaurora.org>,
George Cherian <george.cherian@cavium.com>
Subject: Re: [PATCH v3 3/3] Documentation: intel_pstate: Add base_frequency information
Date: Mon, 15 Oct 2018 08:49:24 -0700 [thread overview]
Message-ID: <c89ff15144f0c24187f82db088622d6c8aebd7d7.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0iXOtcNSqPU7NYwG=S_JCdoTFzLRD1qZocWMnFnVJ-oMQ@mail.gmail.com>
On Mon, 2018-10-15 at 10:53 +0200, Rafael J. Wysocki wrote:
> On Fri, Oct 12, 2018 at 6:44 PM Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> >
> > Updated documentation to explain base_frequency attribute.
> >
> > Signed-off-by: Srinivas Pandruvada <
> > srinivas.pandruvada@linux.intel.com>
> > ---
> > Documentation/admin-guide/pm/intel_pstate.rst | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/admin-guide/pm/intel_pstate.rst
> > b/Documentation/admin-guide/pm/intel_pstate.rst
> > index 8f1d3de449b5..14a5505e073e 100644
> > --- a/Documentation/admin-guide/pm/intel_pstate.rst
> > +++ b/Documentation/admin-guide/pm/intel_pstate.rst
> > @@ -465,6 +465,10 @@ Next, the following policy attributes have
> > special meaning if
> > policy for the time interval between the last two
> > invocations of the
> > driver's utilization update callback by the CPU scheduler
> > for that CPU.
> >
> > +``base_frequency``
> > + When present, shows the base frequency of the CPU. Any
> > frequency above
> > + this will be in the turbo frequency range.
> > +
>
> This isn't entirely correct, because base_frequency is not present in
> the passive mode (and it is not present for the other drivers for
> that
> matter).
That's why it said, "when present". This keeps door open to add to
other modes too in future if needed.
Thanks,
Srinivas
>
> > The meaning of these attributes in the `passive mode <Passive
> > Mode_>`_ is the
> > same as for other scaling drivers.
>
> Instead, I would say:
>
> "One more policy attribute is present if the `HWP feature is enabled
> in the processor <Active Mode With HWP_>`_:"
>
> here and I would add the description of the attribute below.
>
> Thanks,
> Rafael
prev parent reply other threads:[~2018-10-15 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 16:43 [PATCH v3 0/3] cpufreq: intel_pstate: Base frequency attribute Srinivas Pandruvada
2018-10-12 16:43 ` [PATCH v3 1/3] ACPI / CPPC: Add support for guaranteed performance Srinivas Pandruvada
2018-10-12 16:43 ` [PATCH v3 2/3] cpufreq: intel_pstate: Add base_frequency attribute Srinivas Pandruvada
2018-10-12 16:44 ` [PATCH v3 3/3] Documentation: intel_pstate: Add base_frequency information Srinivas Pandruvada
2018-10-15 8:53 ` Rafael J. Wysocki
2018-10-15 15:49 ` 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=c89ff15144f0c24187f82db088622d6c8aebd7d7.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=corbet@lwn.net \
--cc=devel@acpica.org \
--cc=erik.schmauss@intel.com \
--cc=george.cherian@cavium.com \
--cc=juri.lelli@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pprakash@codeaurora.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--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).