01 May, 2008
4 commits
-
acpi_device_dir() is NULL until all files are createst, so everyting is
created in straight in /proc/ and creation code warns.Signed-off-by: Alexey Dobriyan
Signed-off-by: Linus Torvalds -
* 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6: (179 commits)
ACPI: Fix acpi_processor_idle and idle= boot parameters interaction
acpi: fix section mismatch warning in pnpacpi
intel_menlo: fix build warning
ACPI: Cleanup: Remove unneeded, multiple local dummy variables
ACPI: video - fix permissions on some proc entries
ACPI: video - properly handle errors when registering proc elements
ACPI: video - do not store invalid entries in attached_array list
ACPI: re-name acpi_pm_ops to acpi_suspend_ops
ACER_WMI/ASUS_LAPTOP: fix build bug
thinkpad_acpi: fix possible NULL pointer dereference if kstrdup failed
ACPI: check a return value correctly in acpi_power_get_context()
#if 0 acpi/bay.c:eject_removable_drive()
eeepc-laptop: add hwmon fan control
eeepc-laptop: add backlight
eeepc-laptop: add base driver
ACPI: thinkpad-acpi: bump up version to 0.20
ACPI: thinkpad-acpi: fix selects in Kconfig
ACPI: thinkpad-acpi: use a private workqueue
ACPI: thinkpad-acpi: fluff really minor fix
ACPI: thinkpad-acpi: use uppercase for "LED" on user documentation
...Fixed conflicts in drivers/acpi/video.c and drivers/misc/intel_menlow.c
manually. -
…-9916', 'ec', 'eeepc', 'idle', 'misc', 'pm-legacy', 'sysfs-links-2.6.26', 'thermal', 'thinkpad' and 'video' into release
-
acpi_processor_idle and "idle=" boot parameter interaction is broken.
The problem is that, at boot time acpi driver is checking for "idle=" boot
option and not registering the acpi idle handler. But, when there is a CST
changed callback (typically when switching AC battery or suspend-resume)
there are no checks for boot_option_idle_override and acpi idle handler tries
to get installed with nasty side effects.With CPU_IDLE configured this issue causes results in a nasty oops on CST
change callback and without CPU_IDLE there is no oops, but boot option
of "idle=" gets ignored and acpi idle handler gets installed.Change the behavior to not do anything in acpi idle handler when there is a
"idle=" boot option.Note that the problem is only there when "idle=" boot option is used.
Signed-off-by: Venkatesh Pallipadi
Signed-off-by: Len Brown
30 Apr, 2008
1 commit
-
Legacy HP ia64 platforms currently cannot provide
/proc/cpuinfo/physical_id due to legacy SAL/PAL implementations.
However, that physical topology information can be obtained
via ACPI.Provide an interface that gives ACPI one last chance to provide
physical_id for these legacy platforms. This logic only comes
into play iff:- ACPI actually provides slot information for the CPU
- we lack a valid socket_idOtherwise, we don't do anything.
Since x86 uses the ACPI processor driver as well, we provide a nop
stub function for arch_fix_phys_package_id() in asm-x86/topology.hSigned-off-by: Alex Chiang
Signed-off-by: Tony Luck
29 Apr, 2008
17 commits
-
…nux-2.6-x86-bigbox-pci
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86-bigbox-pci:
x86: add pci=check_enable_amd_mmconf and dmi check
x86: work around io allocation overlap of HT links
acpi: get boot_cpu_id as early for k8_scan_nodes
x86_64: don't need set default res if only have one root bus
x86: double check the multi root bus with fam10h mmconf
x86: multi pci root bus with different io resource range, on 64-bit
x86: use bus conf in NB conf fun1 to get bus range on, on 64-bit
x86: get mp_bus_to_node early
x86 pci: remove checking type for mmconfig probe
x86: remove unneeded check in mmconf reject
driver core: try parent numa_node at first before using default
x86: seperate mmconf for fam10h out from setup_64.c
x86: if acpi=off, force setting the mmconf for fam10h
x86_64: check MSR to get MMCONFIG for AMD Family 10h
x86_64: check and enable MMCONFIG for AMD Family 10h
x86_64: set cfg_size for AMD Family 10h in case MMCONFIG
x86: mmconf enable mcfg early
x86: clear pci_mmcfg_virt when mmcfg get rejected
x86: validate against acpi motherboard resourcesFixed up fairly trivial conflicts in arch/x86/pci/{init.c,pci.h} due to
OLPC support manually. -
Use proc_create()/proc_create_data() to make sure that ->proc_fops and ->data
be setup before gluing PDE to main tree.Add correct ->owner to proc_fops to fix reading/module unloading race.
Signed-off-by: Denis V. Lunev
Cc: Len Brown
Cc: Alexey Dobriyan
Cc: "Eric W. Biederman"
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Signed-off-by: Thomas Renninger
Signed-off-by: Len Brown -
POST and DOS are supposed to be writable but permissions
did not allow it.Signed-off-by: Dmitry Torokhov
Acked-by: Zhang Rui
Signed-off-by: Len Brown -
Have acpi_video_device_add_fs() and acpi_video_bus_add_fs()
properly unwind proc creation after error.Signed-off-by: Dmitry Torokhov
Acked-by: Zhang Rui
Signed-off-by: Len Brown -
this is a cleanup, not a change to function.
Signed-off-by: Dmitry Torokhov
Acked-by: Zhang Rui
Signed-off-by: Len Brown -
... as they are platform_suspend_ops after all.
cosmetic re-name only, no functional change.
Signed-off-by: Len Brown
-
We should check *resource != NULL rather than resource != NULL, which will be
always true.Signed-off-by: Li Zefan
Acked-by: Zhao Yakui
Signed-off-by: Andrew Morton
Signed-off-by: Len Brown -
This patch #if 0's the unused eject_removable_drive().
Signed-off-by: Adrian Bunk
Signed-off-by: Len Brown -
acpi_ev_disable_gpe() has an optimization where it doesn't disable
a GPE that it "doesn't have to". Unfortunately, it can get tricked
by AML that scribbles on register state behind its back. So when asked
to disable a GPE, simply do it -- a redundant register write
in the common case is a fair price to pay to be bomb-proof
for the rare cases.http://bugzilla.kernel.org/show_bug.cgi?id=6217
Signed-off-by: Damián Viano
Acked-by: Zhang Rui
Signed-off-by: Len Brown -
Fix the problem that thermal_get_temp returns the cached value,
which causes the temperature in generic thermal never updates.Signed-off-by: Zhang Rui
Acked-by: Jean Delvare
Signed-off-by: Len Brown -
thermal_cooling_device_register used to return NULL if THERMAL is "n".
As the ACPI fan, processor and video drivers SELECT the generic
thermal in PATCH 01, this is not a problem any more.Signed-off-by: Julia Lawall
Signed-off-by: Zhang Rui
Signed-off-by: Len Brown -
Update the documentation for the thermal driver hwmon sys I/F.
Change the ACPI thermal zone type to be consistent with hwmon.
Signed-off-by: Zhang Rui
Acked-by: Jean Delvare
Signed-off-by: Len Brown -
Add a new callback so that the generic thermal can get
the critical trip point info of a thermal zone,
which is needed for building the tempX_crit hwmon sysfs attribute.Signed-off-by: Zhang Rui
Acked-by: Jean Delvare
Signed-off-by: Len Brown -
Build the generic thermal driver as module "thermal_sys".
Make ACPI thermal, video, processor and fan SELECT the generic
thermal driver, as these drivers rely on it to build the sysfs I/F.Signed-off-by: Zhang Rui
Acked-by: Jean Delvare
Signed-off-by: Len Brown -
Flush kacpi_notify_wq before notify handler is removed,
this can fix a bug which the deferred notify handler is executed
after the notify_handler has already been removed.
http://bugzilla.kernel.org/show_bug.cgi?id=9772Signed-off-by: Zhang Rui
Signed-off-by: Len Brown -
Change cpufreq tables from arrays to per_cpu variables in
drivers/acpi/processor_thermal.cBased on git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Cc: Len Brown
Signed-off-by: Mike Travis
Signed-off-by: Dave Jones
28 Apr, 2008
1 commit
-
drivers/acpi/thermal.c: In function 'acpi_thermal_init':
drivers/acpi/thermal.c:1794: error: 'thermal_dmi_table' undeclared (first use in this function)
drivers/acpi/thermal.c:1794: error: (Each undeclared identifier is reported only once
drivers/acpi/thermal.c:1794: error: for each function it appears in.)Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
27 Apr, 2008
2 commits
-
OK, so 25-mm1 gave a lockdep error which made me look into this.
The first thing that I noticed was the horrible mess; the second thing I
saw was hacks like: 71e93d15612c61c2e26a169567becf088e71b8ffThe problem is that arch idle routines are somewhat inconsitent with
their IRQ state handling and instead of fixing _that_, we go paper over
the problem.So the thing I've tried to do is set a standard for idle routines and
fix them all up to adhere to that. So the rules are:idle routines are entered with IRQs disabled
idle routines will exit with IRQs enabledNearly all already did this in one form or another.
Merge the 32 and 64 bit bits so they no longer have different bugs.
As for the actual lockdep warning; __sti_mwait() did a plainly un-annotated
irq-enable.Signed-off-by: Peter Zijlstra
Tested-by: Bob Copeland
Signed-off-by: Ingo Molnar -
This path adds validation of the MMCONFIG table against the ACPI reserved
motherboard resources. If the MMCONFIG table is found to be reserved in
ACPI, we don't bother checking the E820 table. The PCI Express firmware
spec apparently tells BIOS developers that reservation in ACPI is required
and E820 reservation is optional, so checking against ACPI first makes
sense. Many BIOSes don't reserve the MMCONFIG region in E820 even though
it is perfectly functional, the existing check needlessly disables MMCONFIG
in these cases.In order to do this, MMCONFIG setup has been split into two phases. If PCI
configuration type 1 is not available then MMCONFIG is enabled early as
before. Otherwise, it is enabled later after the ACPI interpreter is
enabled, since we need to be able to execute control methods in order to
check the ACPI reserved resources. Presently this is just triggered off
the end of ACPI interpreter initialization.There are a few other behavioral changes here:
- Validate all MMCONFIG configurations provided, not just the first one.
- Validate the entire required length of each configuration according to
the provided ending bus number is reserved, not just the minimum required
allocation.- Validate that the area is reserved even if we read it from the chipset
directly and not from the MCFG table. This catches the case where the
BIOS didn't set the location properly in the chipset and has mapped it
over other things it shouldn't have.This also cleans up the MMCONFIG initialization functions so that they
simply do nothing if MMCONFIG is not compiled in.Based on an original patch by Rajesh Shah from Intel.
[akpm@linux-foundation.org: many fixes and cleanups]
Signed-off-by: Robert Hancock
Signed-off-by: Andi Kleen
Cc: Andrew Morton
Cc: Greg KH
Signed-off-by: Thomas Gleixner
Tested-by: Andi Kleen
Cc: Rajesh Shah
Cc: Jesse Barnes
Acked-by: Linus Torvalds
Cc: Andi Kleen
Cc: Greg KH
Signed-off-by: Ingo Molnar
Signed-off-by: Andrew Morton
Signed-off-by: Thomas Gleixner
25 Apr, 2008
2 commits
-
Patch to fix huge number of wakeups reported due to recent changes in
processor_idle.c. The problem was that the entry_method determination was
broken due to one of the recent commits (bc71bec91f987) causing
C1 entry to not to go to halt.http://lkml.org/lkml/2008/3/22/124
Signed-off-by: Venkatesh Pallipadi
Signed-off-by: Len Brown -
GPE could try to access EC region, so should not be enabled before
EC is installedhttp://bugzilla.kernel.org/show_bug.cgi?id=9916
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown
24 Apr, 2008
1 commit
-
Signed-off-by: Len Brown
23 Apr, 2008
12 commits
-
Fixed a problem with the CreateField, CreateXXXField (Bit, Byte,
Word, Dword, Qword), Field, BankField, and IndexField operators
when invoked from inside an executing control method. In this case,
these operators created namespace nodes that were incorrectly
left marked as permanent nodes instead of temporary nodes. This
could cause a problem if there is race condition between an
exiting control method and a running namespace walk. (Reported
by Linn Crosetto). Fixed a problem where the CreateField and
CreateXXXField operators would incorrectly allow duplicate names
(the name of the field) with no exception generated.Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
Implemented several changes for Notify handling: Added support
for new Notify values (ACPI 2.0+) and improved the Notify debug
output. Notify on PowerResource objects is no longer allowed,
as per the ACPI specification.Signed-off-by: Zhang Rui
Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
Fixed a couple of size calculation issues with the variable-length
Start Dependent resource descriptor.Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
Implemented several improvements for the output of the ASL "Debug"
object to clarify and keep all data for a given object on one
output line.Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
All Reference Objects returned via the AcpiEvaluteObject interface
are now marked as type "REFERENCE" instead of "ANY". The type ANY
is now reservered for NULL objects - either NULL package elements
or unresolved named references.Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Lin Ming
Signed-off-by: Len Brown -
Fixed problem where NULL package elements were not returned to
the AcpiEvaluateObject interface correctly. Instead of returning a
NULL ACPI_OBJECT package element, the element was simply ignored,
potentially causing a buffer overflow and/or confusing the caller
who expected a fixed number of elements.http://bugzilla.kernel.org/show_bug.cgi?id=10132
Signed-off-by: Lin Ming
Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
Fixed a problem where an extraneous debug message was produced for
package objects (when debugging enabled). The message "Package
List length larger than NumElements count" is now produced in
the correct case, and is also an error message rather than a
debug message. Added a debug message for the opposite case, where
NumElements is larger than the Package List, and the package has
been padded out with NULL elements.Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
Fixed a problem where buffer and package objects passed as
arguments to a control method via the external AcpiEvaluateObject
interface could cause an AE_AML_INTERNAL exception depending on the
order and type of operators executed by the target control method.Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
Fixed a problem where a CopyObject to RegionField, BankField, and
IndexField objects did not perform an implicit conversion as it
should. These types must retain their initial type permanently as
per the ACPI specification. However, a CopyObject to all other
object types should not perform an implicit conversion, as per
the ACPI specification.http://www.acpica.org/bugzilla/show_bug.cgi?id=388
Signed-off-by: Lin Ming
Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
Fixed a problem where resource descriptor size optimization
could cause a problem when a _CRS resource template is passed
to a _SRS method. The _SRS resource template must use the same
descriptors (with the same size) as returned from _CRS. This
change affects the following resource descriptors: IRQ/IRQNoFlags
and StartDependendentFn/StartDependentFnNoPri.http://bugzilla.kernel.org/show_bug.cgi?id=9487
Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
New messages for the 2 AE_SUPPORT cases.
Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown -
Added missing va_end statements that should correspond with each
va_start statement.Signed-off-by: Bob Moore
Signed-off-by: Alexey Starikovskiy
Signed-off-by: Len Brown
