linux-toradex.git/drivers/acpi, branch v2.6.19

[PATCH] Correct bound checking from the value returned from _PPC method.

2006-11-23T17:18:55+00:00

processor_perflib.c::acpi_processor_ppc_notifier() check if the value
returned by the processor's _PPC method is 0 and return failed if so.
This is wrong since 0 indicate that the bios think the processor can go
to the highest frequency.  This patch for example fix the HP NX 6125 to
allow its highest frequency to be available.

Signed-off-by: Bruno Ducrot 
Cc: "Pallipadi, Venkatesh" 
Signed-off-by: Dave Jones 
Signed-off-by: Linus Torvalds

Revert "ACPI: created a dedicated workqueue for notify() execution"

2006-11-18T03:31:09+00:00

This reverts commit 37605a6900f6b4d886d995751fcfeef88c4e462c.

Again.

This same bug has now been introduced twice: it was done earlier by
commit b8d35192c55fb055792ff0641408eaaec7c88988, only to be reverted
last time in commit 72945b2b90a5554975b8f72673ab7139d232a121.

We must NOT try to queue up notify handlers to another thread than the
normal ACPI execution thread, because the notifications on some systems
seem to just keep on accumulating until we run out of memory and/or
threads.

Keeping events within the one deferred execution thread automatically
throttles the events properly.

At least the Compaq N620c will lock up completely on the first thermal
event without this patch reverted.

Cc: David Brownell 
Cc: Len Brown 
Cc: Alexey Starikovskiy 
Signed-off-by: Linus Torvalds

[PATCH] acpi memory hotplug: remove strange add_memory fail message

2006-10-20T17:26:38+00:00

I wrote a patch to avoid redundant memory hot-add call at boot time.  This
was cause of strange fail message of memory hotplug like "ACPI: add_memory
failed".  Memory is recognized by early boot code with EFI/E820.

But, if DSDT describes memory devices for them, then hot-add code is called
for already recognized memory, and it shows fail messages with -EEXIST.
So, sys admin will misunderstand this message as something wrong by it.

This patch avoids them by preventing redundant hot-add call until
completion of driver initialization.

[akpm@osdl.org: cleanups]
Signed-off-by: Yasunori Goto 
Cc: "Brown, Len" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] Change log level of a message of acpi_memhotplug to KERN_DEBUG

2006-10-20T17:26:37+00:00

I suppose this message seems quite useless except debugging.  It just shows
"Hotplug Mem Device".  System admin can't know anything by this message.
So, I would like to change it to KERN_DEBUG.

Signed-off-by: Yasunori Goto 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] fix "ACPI: Processor native C-states using MWAIT"

2006-10-20T17:26:37+00:00

This patch breaks C-state discovery on my IBM IntelliStation Z30 because
the return value of acpi_processor_get_power_info_fadt is not assigned to
"result" in the case that acpi_processor_get_power_info_cst returns
-ENODEV.  Thus, if ACPI provides C-state data via the FADT and not _CST (as
is the case on this machine), we incorrectly exit the function with -ENODEV
after reading the FADT.  The attached patch sets the value of result so
that we don't exit early.

Signed-off-by: Darrick J. Wong 
Acked-by: "Pallipadi, Venkatesh" 
Acked-by: "Brown, Len" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] acpi_processor_latency_notifier(): UP warning fix

2006-10-17T15:18:44+00:00

drivers/acpi/processor_idle.c:1112: warning: 'smp_callback' defined but not used

Cc: Len Brown 
Cc: Arjan van de Ven 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Pull trivial into test branch

2006-10-14T06:28:07+00:00

Pull bugzilla-5534 into test branch

2006-10-14T06:26:42+00:00

Pull ec into test branch

2006-10-14T06:26:10+00:00

Pull mwait into test branch

2006-10-14T06:25:59+00:00