kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: yakui_zhao <yakui.zhao@intel.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Alexey Starikovskiy <aystarik@gmail.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: [BISECTED] 20 ACPI interrupts per second on EEEPC 4G
Date: Mon, 13 Apr 2009 18:05:31 +0100	[thread overview]
Message-ID: <20090413170531.GA13188@srcf.ucam.org> (raw)
In-Reply-To: <49E3085D.3060403@tuffmail.co.uk>

Ok, I think I've got it. Does this fix things? Ridiculous thinko...

diff --git a/drivers/acpi/thermal.c b/drivers/acpi/thermal.c
index 9cd15e8..564ea14 100644
--- a/drivers/acpi/thermal.c
+++ b/drivers/acpi/thermal.c
@@ -909,7 +909,7 @@ static int acpi_thermal_register_thermal_zone(struct acpi_thermal *tz)
 			thermal_zone_device_register("acpitz", trips, tz,
 						     &acpi_thermal_zone_ops,
 						     0, 0, 0,
-						     tz->polling_frequency);
+						     tz->polling_frequency*100);
 	if (IS_ERR(tz->thermal_zone))
 		return -ENODEV;
 

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-04-13 17:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-10 15:39 Regression: 20 ACPI interrupts per second on EEEPC 4G Alan Jenkins
     [not found] ` <49DF6835.9040501-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2009-04-11  0:24   ` Alexey Starikovskiy
2009-04-11  9:14     ` Alan Jenkins
     [not found]       ` <49E05F83.2090500-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2009-04-12 15:54         ` [BISECTED] " Alan Jenkins
     [not found]           ` <49E20EBA.2090708-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2009-04-13  2:04             ` yakui_zhao
     [not found]               ` <1239588248.5564.19.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-04-13  9:39                 ` Alan Jenkins
2009-04-13 17:05                   ` Matthew Garrett [this message]
2009-04-13 17:43                     ` Joe Perches
     [not found]                     ` <20090413170531.GA13188-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-04-13 18:42                       ` Alan Jenkins
2009-04-14 19:16                         ` [PATCH] thermal: Fix polling frequency for systems without passive cooling Matthew Garrett
     [not found]                           ` <20090414191645.GB7940-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-04-17  1:37                             ` Zhang Rui
2009-04-18  5:05                               ` Len Brown
2009-04-13 14:53             ` [BISECTED] 20 ACPI interrupts per second on EEEPC 4G Matthew Garrett
2009-04-13  2:06           ` Zhang Rui
2009-04-17 20:54           ` Alexey Starikovskiy

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=20090413170531.GA13188@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=aystarik@gmail.com \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=yakui.zhao@intel.com \
    /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).