Hi,
be careful, this could break the T60 again.
Can you and Ingo place acpidump of your machines somewhere, please.
On Thursday 16 April 2009 02:27:12 Darrick J. Wong wrote:
This is wrong. _PPC is only evaluated when a cpufreq driver got registered.
Your machine should suffer from that since Ingo's T60 patch?
Reading the _PPC part of the ACPI spec again:
---
In order to support dynamic changes of _PPC object, Notify events on
the processor object. Notify events of type 0x80 will cause OSPM to
reevaluate any _PPC objects residing under the particular processor object
notified.
---
The *reevaluate* implies that the _PPC value has been evaluated/initialized
by the OS already and Ingo's patch would be wrong then.
I'd like to have a look at the T60's ACPI parts and find out what exactly
(or if at all) makes _PPC to return sane values, I expect it's _PDC.
Hmm, I could also imagine that Ingo's T60 patch is not needed anymore since
Yakui's patch (0ac3c571315a53c14d2733564f14ebdb911fe903).
This one could make sure that _PDC is evaluated first making the internal
ACPI _PPC state initialize and makes sure _PPC gets only called afterwards.
If this patch does not break Ingo's T60, I think this should go in.
Due to Yakui's reordering/cleanup of ACPI function calls, I think also
the notifier chain I introduced is not needed anymore and I can clean this
up if I find some time.
You are more or less reverting Ingo's patch (e4233dec749a3519069d9390561b5636a75c7579):
diff --git a/drivers/acpi/processor_perflib.c b/drivers/acpi/processor_perflib.c
index 5207f9e..cbb6f08 100644
--- a/drivers/acpi/processor_perflib.c
+++ b/drivers/acpi/processor_perflib.c
@@ -322,10 +322,6 @@ static int acpi_processor_get_performance_info(struct acpi_processor *pr)
if (result)
return result;
- result = acpi_processor_get_platform_limit(pr);
- if (result)
- return result;
-
return 0;
}
Thomas
--