All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] cpufreq powernow-k8: Remove firmware warning in zero transition latency case
@ 2011-06-08  8:07 Thomas Renninger
  2011-06-08 13:55 ` Dave Jones
  0 siblings, 1 reply; 3+ messages in thread
From: Thomas Renninger @ 2011-06-08  8:07 UTC (permalink / raw)
  To: davej; +Cc: cpufreq

AMD's BKDG documents that a zero transition latency should get passed for
several recent CPU models.
-> This isn't a firmware bug.

I did not dare to really pass the zero latency to the cpufreq core,
this would need careful checking whether this does not show side effects.
-> Still modify latency to 1 (us) in case BIOS passes zero.

Signed-off-by: Thomas Renninger <trenn@suse.de>
CC: cpufreq@vger.kernel.org
CC: davej@codemonkey.org.uk

---
 drivers/cpufreq/powernow-k8.c |   13 ++-----------
 1 files changed, 2 insertions(+), 11 deletions(-)

diff --git a/drivers/cpufreq/powernow-k8.c b/drivers/cpufreq/powernow-k8.c
index 83479b6..170ad36 100644
--- a/drivers/cpufreq/powernow-k8.c
+++ b/drivers/cpufreq/powernow-k8.c
@@ -1022,18 +1022,9 @@ static int get_transition_latency(struct powernow_k8_data *data)
 		if (cur_latency > max_latency)
 			max_latency = cur_latency;
 	}
-	if (max_latency == 0) {
-		/*
-		 * Fam 11h and later may return 0 as transition latency. This
-		 * is intended and means "very fast". While cpufreq core and
-		 * governors currently can handle that gracefully, better set it
-		 * to 1 to avoid problems in the future.
-		 */
-		if (boot_cpu_data.x86 < 0x11)
-			printk(KERN_ERR FW_WARN PFX "Invalid zero transition "
-				"latency\n");
+	if (max_latency == 0)
 		max_latency = 1;
-	}
+
 	/* value in usecs, needs to be in nanoseconds */
 	return 1000 * max_latency;
 }

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] cpufreq powernow-k8: Remove firmware warning in zero transition latency case
  2011-06-08  8:07 [PATCH] cpufreq powernow-k8: Remove firmware warning in zero transition latency case Thomas Renninger
@ 2011-06-08 13:55 ` Dave Jones
  2011-06-08 14:46   ` Thomas Renninger
  0 siblings, 1 reply; 3+ messages in thread
From: Dave Jones @ 2011-06-08 13:55 UTC (permalink / raw)
  To: Thomas Renninger; +Cc: cpufreq

On Wed, Jun 08, 2011 at 10:07:13AM +0200, Thomas Renninger wrote:
 > AMD's BKDG documents that a zero transition latency should get passed for
 > several recent CPU models.
 > -> This isn't a firmware bug.

but the test you're deleting is checking for family < 11h. 
My reading of that comment is that it _was_ a firmware bug on earlier systems.

	Dave 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] cpufreq powernow-k8: Remove firmware warning in zero transition latency case
  2011-06-08 13:55 ` Dave Jones
@ 2011-06-08 14:46   ` Thomas Renninger
  0 siblings, 0 replies; 3+ messages in thread
From: Thomas Renninger @ 2011-06-08 14:46 UTC (permalink / raw)
  To: Dave Jones; +Cc: cpufreq

On Wednesday, June 08, 2011 03:55:27 PM Dave Jones wrote:
> On Wed, Jun 08, 2011 at 10:07:13AM +0200, Thomas Renninger wrote:
>  > AMD's BKDG documents that a zero transition latency should get passed
>  > for several recent CPU models.
>  > -> This isn't a firmware bug.
> 
> but the test you're deleting is checking for family < 11h. 
Eh, right. And in 2.6.32 we had:
-               if (boot_cpu_data.x86 != 0x11)
which I now removed and wanted to submit mainline...

> My reading of that comment is that it _was_ a firmware bug on earlier
> systems.

Not sure whether earlier systems really showed this, but
the test is correct, you can ignore the patch.

Thanks for pointing that out,

   Thomas

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-06-08 14:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-08  8:07 [PATCH] cpufreq powernow-k8: Remove firmware warning in zero transition latency case Thomas Renninger
2011-06-08 13:55 ` Dave Jones
2011-06-08 14:46   ` Thomas Renninger

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.