From: Viresh Kumar <viresh.kumar@linaro.org>
To: Thomas Renninger <trenn@suse.de>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
thomas.mingarelli@hp.com
Subject: Re: CPUFREQ: Try to load pcc driver on HP ProLiants automatically
Date: Thu, 24 Apr 2014 09:34:40 +0530 [thread overview]
Message-ID: <CAKohpokrtVQP80Go+Y3KX45t6P5Vj0tpDu-7f=84puE+6SfwZg@mail.gmail.com> (raw)
In-Reply-To: <7669060.dKLoxkfpfu@skinner>
As Rafael picks patches from patchworks, you may need to resend it to
linux-pm, for now I have cc'id it.
On 23 April 2014 19:19, Thomas Renninger <trenn@suse.de> wrote:
> HP ProLiants are sold with CPU frequency controlled by BIOS by default.
> The pcc-cpufreq driver still exports some frequency info to userspace and
> should be tried to get loaded on these platforms.
>
> Successfully tested on a recent ProLiant machine:
> - without this patch no pcc-cpufreq driver loaded, no frequency info
> - with this patch the driver got autoloaded
>
> Signed-off-by: Thomas Renninger <trenn@suse.de>
>
> diff --git a/drivers/cpufreq/pcc-cpufreq.c b/drivers/cpufreq/pcc-cpufreq.c
> index 728a2d8..ff1ebd0 100644
> --- a/drivers/cpufreq/pcc-cpufreq.c
> +++ b/drivers/cpufreq/pcc-cpufreq.c
> @@ -603,6 +603,8 @@ static void __exit pcc_cpufreq_exit(void)
> free_percpu(pcc_cpu_info);
> }
>
> +MODULE_ALIAS("dmi:*:svnHP:pnProLiant*:*");
> +
> MODULE_AUTHOR("Matthew Garrett, Naga Chumbalkar");
> MODULE_VERSION(PCC_VERSION);
> MODULE_DESCRIPTION("Processor Clocking Control interface driver");
>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
prev parent reply other threads:[~2014-04-24 4:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 13:49 CPUFREQ: Try to load pcc driver on HP ProLiants automatically Thomas Renninger
2014-04-24 4:04 ` Viresh Kumar [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='CAKohpokrtVQP80Go+Y3KX45t6P5Vj0tpDu-7f=84puE+6SfwZg@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=thomas.mingarelli@hp.com \
--cc=trenn@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).