From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Rafal Bilski <rafalbilski@interia.pl>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
Dave Jones <davej@redhat.com>
Subject: Re: [PATCH] Longhaul: Disable driver by default
Date: Tue, 27 Nov 2012 23:33:10 +0100 [thread overview]
Message-ID: <1997813.IluQxocScm@vostro.rjw.lan> (raw)
In-Reply-To: <1354054435-2459-1-git-send-email-rafalbilski@interia.pl>
On Tuesday, November 27, 2012 10:13:55 PM Rafal Bilski wrote:
> This is only solution I can think of. User decides if he wants this
> driver on his machine. I don't have enough knowledge and time to find
> the reason why same code works on some machines and doesn't on others
> which use same, or very similar, chipset and processor.
I always have problems with patches like this one, because they are pretty much
guaranteed to make someone complain.
Is there any way to blacklist the affected machine you have?
Rafael
> Signed-off-by: Rafal Bilski <rafalbilski@interia.pl>
>
> ---
> drivers/cpufreq/longhaul.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/longhaul.c b/drivers/cpufreq/longhaul.c
> index 53ddbc7..0bf5bd1 100644
> --- a/drivers/cpufreq/longhaul.c
> +++ b/drivers/cpufreq/longhaul.c
> @@ -77,7 +77,7 @@ static unsigned int longhaul_index;
> static int scale_voltage;
> static int disable_acpi_c3;
> static int revid_errata;
> -
> +static int enable;
>
> /* Clock ratios multiplied by 10 */
> static int mults[32];
> @@ -965,6 +965,10 @@ static int __init longhaul_init(void)
> if (!x86_match_cpu(longhaul_id))
> return -ENODEV;
>
> + if (!enable) {
> + printk(KERN_ERR PFX "Option \"enable\" not set. Aborting.\n");
> + return -ENODEV;
> + }
> #ifdef CONFIG_SMP
> if (num_online_cpus() > 1) {
> printk(KERN_ERR PFX "More than 1 CPU detected, "
> @@ -1021,6 +1025,10 @@ MODULE_PARM_DESC(scale_voltage, "Scale voltage of processor");
> * such. */
> module_param(revid_errata, int, 0644);
> MODULE_PARM_DESC(revid_errata, "Ignore CPU Revision ID");
> +/* By default driver is disabled to prevent incompatible
> + * system freeze. */
> +module_param(enable, int, 0644);
> +MODULE_PARM_DESC(enable, "Enable driver");
>
> MODULE_AUTHOR("Dave Jones <davej@redhat.com>");
> MODULE_DESCRIPTION("Longhaul driver for VIA Cyrix processors.");
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2012-11-27 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 22:13 [PATCH] Longhaul: Disable driver by default Rafal Bilski
2012-11-27 22:33 ` Rafael J. Wysocki [this message]
2012-11-27 22:41 ` Dave Jones
2012-11-27 23:38 ` Rafał Bilski
2012-11-27 23:44 ` Rafael J. Wysocki
2012-12-15 0:06 ` Rafael J. Wysocki
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=1997813.IluQxocScm@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafalbilski@interia.pl \
/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