[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52C722A7.5070001@infradead.org>
Date: Fri, 03 Jan 2014 12:50:47 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Ramkumar Ramachandra <artagnon@...il.com>,
LKML <linux-kernel@...r.kernel.org>
CC: Dirk Brandewie <dirk.brandewie@...il.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux PM <linux-pm@...r.kernel.org>
Subject: Re: [PATCH v2] Documentation/cpu-freq: add intel-pstate.txt
On 01/03/14 11:23, Ramkumar Ramachandra wrote:
>
> Documentation/cpu-freq/intel-pstate.txt | 40 +++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/cpu-freq/intel-pstate.txt
>
> diff --git a/Documentation/cpu-freq/intel-pstate.txt b/Documentation/cpu-freq/intel-pstate.txt
> new file mode 100644
> index 0000000..69bc26a
> --- /dev/null
> +++ b/Documentation/cpu-freq/intel-pstate.txt
> @@ -0,0 +1,40 @@
> +Intel P-state driver
> +--------------------
> +
> +This driver implements a scaling driver with an internal governor for
> +Intel Core processors. The driver follows the same model as the
> +Transmeta scaling driver (longrun.c) and implements the setpolicy()
> +instead of target(). Scaling drivers that implement setpolicy() are
> +assmumed to implement internal governors by the cpufreq core. All the
assumed
Fix that and then you can add:
Acked-by: Randy Dunlap <rdunlap@...radead.org>
Thanks.
> +logic for selecting the current P state is contained within the
> +driver; no external governor is used by the cpufreq core.
> +
> +Intel SandyBridge+ processors are supported.
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists