linux-toradex.git/drivers/acpi, branch v3.3.5

ACPICA: Fix regression in FADT revision checks

2012-04-13T16:13:52+00:00

commit 3e80acd1af40fcd91a200b0416a7616b20c5d647 upstream.

	commit 64b3db22c04586997ab4be46dd5a5b99f8a2d390 (2.6.39),
"Remove use of unreliable FADT revision field" causes regression
for old P4 systems because now cst_control and other fields are
not reset to 0.

	The effect is that acpi_processor_power_init will notice
cst_control != 0 and a write to CST_CNT register is performed
that should not happen. As result, the system oopses after the
"No _CST, giving up" message, sometimes in acpi_ns_internalize_name,
sometimes in acpi_ns_get_type, usually at random places. May be
during migration to CPU 1 in acpi_processor_get_throttling.

	Every one of these settings help to avoid this problem:
 - acpi=off
 - processor.nocst=1
 - maxcpus=1

	The fix is to update acpi_gbl_FADT.header.length after
the original value is used to check for old revisions.

https://bugzilla.kernel.org/show_bug.cgi?id=42700
https://bugzilla.redhat.com/show_bug.cgi?id=727865

Signed-off-by: Julian Anastasov 
Acked-by: Bob Moore 
Signed-off-by: Len Brown 
Cc: Jonathan Nieder 
Cc: Josh Boyer 
Signed-off-by: Greg Kroah-Hartman

ACPI: Do cpufreq clamping for throttling per package v2

2012-04-13T16:13:52+00:00

commit 2815ab92ba3ab27556212cc306288dc95692824b upstream.

On Intel CPUs the processor typically uses the highest frequency
set by any logical CPU. When the system overheats
Linux first forces the frequency to the lowest available one
to lower the temperature.

However this was done only per logical CPU, which means all
logical CPUs in a package would need to go through this before
the frequency is actually lowered.

Worse this delay actually prevents real throttling, because
the real throttle code only proceeds when the lowest frequency
is already reached.

So when a throttle event happens force the lowest frequency
for all CPUs in the package where it happened. The per CPU
state is now kept per package, not per logical CPU. An alternative
would be to do it per cpufreq unit, but since we want to bring
down the temperature of the complete chip it's better
to do it for all.

In principle it may even make sense to do it for all CPUs,
but I kept it on the package for now.

With this change the frequency is actually lowered, which
in terms also allows real throttling to proceed.

I also removed an unnecessary per cpu variable initialization.

v2: Fix package mapping

Signed-off-by: Andi Kleen 
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

ACPI: remove duplicated lines of merging problems with acpi_processor_add

2012-02-07T22:31:35+00:00

Those lines have two copies.

Signed-off-by: Yinghai Lu 
Cc: Thomas Renninger 
Signed-off-by: Linus Torvalds

Merge branches 'atomicio-apei', 'hotplug', 'sony-nvs-nosave' and 'thermal-netlink' into release

2012-01-24T00:47:06+00:00

Use acpi_os_map_memory() instead of ioremap() in einj driver

2012-01-24T00:39:10+00:00

ioremap() has become more picky and is now spitting out console messages like:

 ioremap error for 0xbddbd000-0xbddbe000, requested 0x10, got 0x0

when loading the einj driver.  What we are trying to so here is map
a couple of data structures that the EINJ table points to. Perhaps
acpi_os_map_memory() is a better tool for this?
Most importantly it works, but as a side benefit it maps the structures
into kernel virtual space so we can access them with normal C memory
dereferences, so instead of using:
	writel(param1, &v5param->apicid);
we can use the more natural:
	v5param->apicid = param1;

Signed-off-by: Tony Luck 
Signed-off-by: Len Brown

ACPI, APEI, EINJ, cleanup 0 vs NULL confusion

2012-01-24T00:38:52+00:00

This function is returning pointers.  Sparse complains here:
drivers/acpi/apei/einj.c:262:32: warning:
	Using plain integer as NULL pointer

Signed-off-by: Dan Carpenter 
Acked-by: Huang Ying 
Signed-off-by: Len Brown

ACPI, APEI, EINJ Allow empty Trigger Error Action Table

2012-01-24T00:31:11+00:00

According to the ACPI spec [1] section 18.6.4 the TRIGGER_ERROR action
table can consists of zero elements.

[1] Advanced Configuration and Power Interface Specification
    Revision 5.0, December 6, 2011
	http://www.acpi.info/DOWNLOADS/ACPIspec50.pdf

Signed-off-by: Niklas Söderlund 
Acked-by: Huang Ying 
Signed-off-by: Len Brown

ACPI / PM: Add Sony Vaio VPCCW29FX to nonvs blacklist.

2012-01-21T06:29:50+00:00

Sony Vaio VPCCW29FX does not resume correctly without
acpi_sleep=nonvs, so add it to the ACPI sleep blacklist.

https://bugzilla.kernel.org/show_bug.cgi?id=34722

Signed-off-by: Lan Tianyu 
Signed-off-by: Len Brown

ACPI: Remove ./drivers/acpi/atomicio.[ch]

2012-01-21T06:09:00+00:00

With the conversion of atomicio's routines in place (see commits
6f68c91c55e and 700130b41f4), atomicio.[ch] can be removed, replacing
the APEI specific pre-mapping capabilities with the more generalized
versions that drivers/acpi/osl.c provides.

Signed-off-by: Myron Stowe 
Signed-off-by: Len Brown

ACPI, APEI: Add RAM mapping support to ACPI

2012-01-21T06:08:38+00:00

This patch adds support for RAM to ACPI's mapping capabilities in order
to support APEI error injection (EINJ) actions.

This patch re-factors similar functionality introduced in commit
76da3fb3575, bringing it into osl.c in preparation for removing
./drivers/acpi/atomicio.[ch].

Signed-off-by: Myron Stowe 
Signed-off-by: Len Brown