2005-04-17 06:20:36 +08:00
|
|
|
#
|
|
|
|
# ACPI Configuration
|
|
|
|
#
|
|
|
|
|
2007-07-03 13:40:59 +08:00
|
|
|
menuconfig ACPI
|
2007-10-30 05:20:38 +08:00
|
|
|
bool "ACPI (Advanced Configuration and Power Interface) Support"
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on !IA64_HP_SIM
|
|
|
|
depends on IA64 || X86
|
2006-03-29 06:04:00 +08:00
|
|
|
depends on PCI
|
2006-12-20 04:56:13 +08:00
|
|
|
depends on PM
|
2007-02-16 11:34:36 +08:00
|
|
|
select PNP
|
2009-02-07 01:24:17 +08:00
|
|
|
select CPU_IDLE
|
2005-04-17 06:20:36 +08:00
|
|
|
default y
|
2009-02-20 05:45:47 +08:00
|
|
|
help
|
2005-04-17 06:20:36 +08:00
|
|
|
Advanced Configuration and Power Interface (ACPI) support for
|
2009-02-20 05:45:47 +08:00
|
|
|
Linux requires an ACPI-compliant platform (hardware/firmware),
|
2005-04-17 06:20:36 +08:00
|
|
|
and assumes the presence of OS-directed configuration and power
|
|
|
|
management (OSPM) software. This option will enlarge your
|
|
|
|
kernel by about 70K.
|
|
|
|
|
|
|
|
Linux ACPI provides a robust functional replacement for several
|
|
|
|
legacy configuration and power management interfaces, including
|
|
|
|
the Plug-and-Play BIOS specification (PnP BIOS), the
|
|
|
|
MultiProcessor Specification (MPS), and the Advanced Power
|
|
|
|
Management (APM) specification. If both ACPI and APM support
|
2009-02-20 05:45:47 +08:00
|
|
|
are configured, ACPI is used.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
The project home page for the Linux ACPI subsystem is here:
|
|
|
|
<http://www.lesswatts.org/projects/acpi/>
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
Linux support for ACPI is based on Intel Corporation's ACPI
|
2009-02-20 05:45:47 +08:00
|
|
|
Component Architecture (ACPI CA). For more information on the
|
|
|
|
ACPI CA, see:
|
|
|
|
<http://acpica.org/>
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
ACPI is an open industry specification co-developed by
|
|
|
|
Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba.
|
|
|
|
The specification is available at:
|
2005-04-17 06:20:36 +08:00
|
|
|
<http://www.acpi.info>
|
|
|
|
|
2005-05-27 16:53:27 +08:00
|
|
|
if ACPI
|
|
|
|
|
2007-07-28 15:33:16 +08:00
|
|
|
config ACPI_SLEEP
|
|
|
|
bool
|
2008-10-23 02:58:43 +08:00
|
|
|
depends on SUSPEND || HIBERNATION
|
2007-07-28 15:33:16 +08:00
|
|
|
default y
|
|
|
|
|
2007-01-29 11:02:30 +08:00
|
|
|
config ACPI_PROCFS
|
2007-07-24 13:50:46 +08:00
|
|
|
bool "Deprecated /proc/acpi files"
|
|
|
|
depends on PROC_FS
|
2009-02-20 05:45:47 +08:00
|
|
|
help
|
2007-07-24 13:50:46 +08:00
|
|
|
For backwards compatibility, this option allows
|
2007-10-20 09:10:57 +08:00
|
|
|
deprecated /proc/acpi/ files to exist, even when
|
2007-07-24 13:50:46 +08:00
|
|
|
they have been replaced by functions in /sys.
|
|
|
|
The deprecated files (and their replacements) include:
|
|
|
|
|
2007-07-24 14:16:50 +08:00
|
|
|
/proc/acpi/sleep (/sys/power/state)
|
2009-02-20 05:45:47 +08:00
|
|
|
/proc/acpi/info (/sys/module/acpi/parameters/acpica_version)
|
2007-07-24 13:50:46 +08:00
|
|
|
/proc/acpi/dsdt (/sys/firmware/acpi/tables/DSDT)
|
|
|
|
/proc/acpi/fadt (/sys/firmware/acpi/tables/FACP)
|
|
|
|
/proc/acpi/debug_layer (/sys/module/acpi/parameters/debug_layer)
|
|
|
|
/proc/acpi/debug_level (/sys/module/acpi/parameters/debug_level)
|
2009-06-24 11:49:49 +08:00
|
|
|
/proc/acpi/processor/*/power (/sys/devices/system/cpu/*/cpuidle/*)
|
|
|
|
/proc/acpi/processor/*/performance (/sys/devices/system/cpu/*/
|
|
|
|
cpufreq/*)
|
|
|
|
/proc/acpi/processor/*/throttling (/sys/class/thermal/
|
|
|
|
cooling_device*/*)
|
2007-07-24 13:50:46 +08:00
|
|
|
This option has no effect on /proc/acpi/ files
|
|
|
|
and functions which do not yet exist in /sys.
|
|
|
|
|
|
|
|
Say N to delete /proc/acpi/ files that have moved to /sys/
|
2009-02-20 05:45:47 +08:00
|
|
|
|
2007-11-19 21:33:45 +08:00
|
|
|
config ACPI_PROCFS_POWER
|
2008-01-04 00:31:42 +08:00
|
|
|
bool "Deprecated power /proc/acpi directories"
|
2007-11-19 21:33:45 +08:00
|
|
|
depends on PROC_FS
|
|
|
|
default y
|
2009-02-20 05:45:47 +08:00
|
|
|
help
|
2007-11-19 21:33:45 +08:00
|
|
|
For backwards compatibility, this option allows
|
2008-01-04 00:31:42 +08:00
|
|
|
deprecated power /proc/acpi/ directories to exist, even when
|
2007-11-19 21:33:45 +08:00
|
|
|
they have been replaced by functions in /sys.
|
2008-01-04 00:31:42 +08:00
|
|
|
The deprecated directories (and their replacements) include:
|
2007-11-19 21:33:45 +08:00
|
|
|
/proc/acpi/battery/* (/sys/class/power_supply/*)
|
|
|
|
/proc/acpi/ac_adapter/* (sys/class/power_supply/*)
|
2008-01-04 00:31:42 +08:00
|
|
|
This option has no effect on /proc/acpi/ directories
|
2007-11-19 21:33:45 +08:00
|
|
|
and functions, which do not yet exist in /sys
|
2007-01-29 11:02:30 +08:00
|
|
|
|
2008-01-04 00:31:42 +08:00
|
|
|
Say N to delete power /proc/acpi/ directories that have moved to /sys/
|
|
|
|
|
2009-09-19 03:41:09 +08:00
|
|
|
config ACPI_POWER_METER
|
|
|
|
tristate "ACPI 4.0 power meter"
|
|
|
|
depends on HWMON
|
|
|
|
help
|
|
|
|
This driver exposes ACPI 4.0 power meters as hardware monitoring
|
|
|
|
devices. Say Y (or M) if you have a computer with ACPI 4.0 firmware
|
|
|
|
and a power meter.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called power-meter.
|
|
|
|
|
2008-01-02 03:27:24 +08:00
|
|
|
config ACPI_SYSFS_POWER
|
|
|
|
bool "Future power /sys interface"
|
|
|
|
select POWER_SUPPLY
|
|
|
|
default y
|
2009-02-20 05:45:47 +08:00
|
|
|
help
|
2008-01-02 03:27:24 +08:00
|
|
|
Say N to disable power /sys interface
|
2008-01-04 00:31:42 +08:00
|
|
|
|
2007-08-24 03:20:26 +08:00
|
|
|
config ACPI_PROC_EVENT
|
|
|
|
bool "Deprecated /proc/acpi/event support"
|
|
|
|
depends on PROC_FS
|
2007-08-27 23:04:39 +08:00
|
|
|
default y
|
2009-02-20 05:45:47 +08:00
|
|
|
help
|
|
|
|
A user-space daemon, acpid, typically reads /proc/acpi/event
|
|
|
|
and handles all ACPI-generated events.
|
2007-08-24 03:20:26 +08:00
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
These events are now delivered to user-space either
|
|
|
|
via the input layer or as netlink events.
|
2007-08-24 03:20:26 +08:00
|
|
|
|
2007-08-27 23:04:39 +08:00
|
|
|
This build option enables the old code for legacy
|
2007-08-24 03:20:26 +08:00
|
|
|
user-space implementation. After some time, this will
|
|
|
|
be moved under CONFIG_ACPI_PROCFS, and then deleted.
|
|
|
|
|
2007-08-27 23:04:39 +08:00
|
|
|
Say Y here to retain the old behaviour. Say N if your
|
|
|
|
user-space is newer than kernel 2.6.23 (September 2007).
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_AC
|
|
|
|
tristate "AC Adapter"
|
2007-10-30 05:08:59 +08:00
|
|
|
depends on X86
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver supports the AC Adapter object, which indicates
|
|
|
|
whether a system is on AC or not. If you have a system that can
|
2005-08-26 00:22:04 +08:00
|
|
|
switch between A/C and battery, say Y.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called ac.
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_BATTERY
|
|
|
|
tristate "Battery"
|
2007-10-30 05:08:59 +08:00
|
|
|
depends on X86
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
This driver adds support for battery information through
|
|
|
|
/proc/acpi/battery. If you have a mobile system with a battery,
|
|
|
|
say Y.
|
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called battery.
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_BUTTON
|
|
|
|
tristate "Button"
|
2006-11-09 13:40:13 +08:00
|
|
|
depends on INPUT
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver handles events on the power, sleep, and lid buttons.
|
2005-08-26 00:22:04 +08:00
|
|
|
A daemon reads /proc/acpi/event and perform user-defined actions
|
|
|
|
such as shutting down the system. This is necessary for
|
2009-02-20 05:45:47 +08:00
|
|
|
software-controlled poweroff.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called button.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
config ACPI_VIDEO
|
|
|
|
tristate "Video"
|
2007-05-09 21:07:05 +08:00
|
|
|
depends on X86 && BACKLIGHT_CLASS_DEVICE && VIDEO_OUTPUT_CONTROL
|
2007-09-18 05:41:05 +08:00
|
|
|
depends on INPUT
|
2008-04-21 16:07:13 +08:00
|
|
|
select THERMAL
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver implements the ACPI Extensions For Display Adapters
|
2005-04-17 06:20:36 +08:00
|
|
|
for integrated graphics devices on motherboard, as specified in
|
2009-02-20 05:45:47 +08:00
|
|
|
ACPI 2.0 Specification, Appendix B. This supports basic operations
|
|
|
|
such as defining the video POST device, retrieving EDID information,
|
|
|
|
and setting up a video output.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called video.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
config ACPI_FAN
|
|
|
|
tristate "Fan"
|
2008-04-21 16:07:13 +08:00
|
|
|
select THERMAL
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver supports ACPI fan devices, allowing user-mode
|
2005-04-17 06:20:36 +08:00
|
|
|
applications to perform basic fan control (on, off, status).
|
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called fan.
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
config ACPI_DOCK
|
2008-09-27 11:10:28 +08:00
|
|
|
bool "Dock"
|
2006-07-10 10:09:57 +08:00
|
|
|
depends on EXPERIMENTAL
|
2006-07-10 05:22:28 +08:00
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver supports ACPI-controlled docking stations and removable
|
|
|
|
drive bays such as the IBM Ultrabay and the Dell Module Bay.
|
2006-10-21 05:30:25 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_PROCESSOR
|
|
|
|
tristate "Processor"
|
2008-04-21 16:07:13 +08:00
|
|
|
select THERMAL
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver installs ACPI as the idle handler for Linux and uses
|
|
|
|
ACPI C2 and C3 processor states to save power on systems that
|
2005-08-26 00:22:04 +08:00
|
|
|
support it. It is required by several flavors of cpufreq
|
2009-02-20 05:45:47 +08:00
|
|
|
performance-state drivers.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called processor.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
config ACPI_HOTPLUG_CPU
|
2005-07-30 16:18:00 +08:00
|
|
|
bool
|
|
|
|
depends on ACPI_PROCESSOR && HOTPLUG_CPU
|
2005-04-17 06:20:36 +08:00
|
|
|
select ACPI_CONTAINER
|
2005-07-30 16:18:00 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
|
ACPI: create Processor Aggregator Device driver
ACPI 4.0 created the logical "processor aggregator device" as
a mechinism for platforms to ask the OS to force otherwise busy
processors to enter (power saving) idle.
The intent is to lower power consumption to ride-out
transient electrical and thermal emergencies,
rather than powering off the server.
On platforms that can save more power/performance via P-states,
the platform will first exhaust P-states before forcing idle.
However, the relative benefit of P-states vs. idle states
is platform dependent, and thus this driver need not know
or care about it.
This driver does not use the kernel's CPU hot-plug mechanism
because after the transient emergency is over, the system must
be returned to its normal state, and hotplug would permanently
break both cpusets and binding.
So to force idle, the driver creates a power saving thread.
The scheduler will migrate the thread to the preferred CPU.
The thread has max priority and has SCHED_RR policy,
so it can occupy one CPU. To save power, the thread will
invoke the deep C-state entry instructions.
To avoid starvation, the thread will sleep 5% of the time
time for every second (current RT scheduler has threshold
to avoid starvation, but if other CPUs are idle,
the CPU can borrow CPU timer from other,
which makes the mechanism not work here)
Vaidyanathan Srinivasan has proposed scheduler enhancements
to allow injecting idle time into the system. This driver doesn't
depend on those enhancements, but could cut over to them
when they are available.
Peter Z. does not favor upstreaming this driver until
the those scheduler enhancements are in place. However,
we favor upstreaming this driver now because it is useful
now, and can be enhanced over time.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
NACKed-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2009-07-28 06:11:02 +08:00
|
|
|
config ACPI_PROCESSOR_AGGREGATOR
|
|
|
|
tristate "Processor Aggregator"
|
|
|
|
depends on ACPI_PROCESSOR
|
|
|
|
depends on EXPERIMENTAL
|
2009-09-27 14:35:55 +08:00
|
|
|
depends on X86
|
ACPI: create Processor Aggregator Device driver
ACPI 4.0 created the logical "processor aggregator device" as
a mechinism for platforms to ask the OS to force otherwise busy
processors to enter (power saving) idle.
The intent is to lower power consumption to ride-out
transient electrical and thermal emergencies,
rather than powering off the server.
On platforms that can save more power/performance via P-states,
the platform will first exhaust P-states before forcing idle.
However, the relative benefit of P-states vs. idle states
is platform dependent, and thus this driver need not know
or care about it.
This driver does not use the kernel's CPU hot-plug mechanism
because after the transient emergency is over, the system must
be returned to its normal state, and hotplug would permanently
break both cpusets and binding.
So to force idle, the driver creates a power saving thread.
The scheduler will migrate the thread to the preferred CPU.
The thread has max priority and has SCHED_RR policy,
so it can occupy one CPU. To save power, the thread will
invoke the deep C-state entry instructions.
To avoid starvation, the thread will sleep 5% of the time
time for every second (current RT scheduler has threshold
to avoid starvation, but if other CPUs are idle,
the CPU can borrow CPU timer from other,
which makes the mechanism not work here)
Vaidyanathan Srinivasan has proposed scheduler enhancements
to allow injecting idle time into the system. This driver doesn't
depend on those enhancements, but could cut over to them
when they are available.
Peter Z. does not favor upstreaming this driver until
the those scheduler enhancements are in place. However,
we favor upstreaming this driver now because it is useful
now, and can be enhanced over time.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
NACKed-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2009-07-28 06:11:02 +08:00
|
|
|
help
|
|
|
|
ACPI 4.0 defines processor Aggregator, which enables OS to perform
|
2009-10-09 21:53:24 +08:00
|
|
|
specific processor configuration and control that applies to all
|
ACPI: create Processor Aggregator Device driver
ACPI 4.0 created the logical "processor aggregator device" as
a mechinism for platforms to ask the OS to force otherwise busy
processors to enter (power saving) idle.
The intent is to lower power consumption to ride-out
transient electrical and thermal emergencies,
rather than powering off the server.
On platforms that can save more power/performance via P-states,
the platform will first exhaust P-states before forcing idle.
However, the relative benefit of P-states vs. idle states
is platform dependent, and thus this driver need not know
or care about it.
This driver does not use the kernel's CPU hot-plug mechanism
because after the transient emergency is over, the system must
be returned to its normal state, and hotplug would permanently
break both cpusets and binding.
So to force idle, the driver creates a power saving thread.
The scheduler will migrate the thread to the preferred CPU.
The thread has max priority and has SCHED_RR policy,
so it can occupy one CPU. To save power, the thread will
invoke the deep C-state entry instructions.
To avoid starvation, the thread will sleep 5% of the time
time for every second (current RT scheduler has threshold
to avoid starvation, but if other CPUs are idle,
the CPU can borrow CPU timer from other,
which makes the mechanism not work here)
Vaidyanathan Srinivasan has proposed scheduler enhancements
to allow injecting idle time into the system. This driver doesn't
depend on those enhancements, but could cut over to them
when they are available.
Peter Z. does not favor upstreaming this driver until
the those scheduler enhancements are in place. However,
we favor upstreaming this driver now because it is useful
now, and can be enhanced over time.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
NACKed-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2009-07-28 06:11:02 +08:00
|
|
|
processors in the platform. Currently only logical processor idling
|
|
|
|
is defined, which is to reduce power consumption. This driver
|
2009-10-09 21:53:24 +08:00
|
|
|
supports the new device.
|
ACPI: create Processor Aggregator Device driver
ACPI 4.0 created the logical "processor aggregator device" as
a mechinism for platforms to ask the OS to force otherwise busy
processors to enter (power saving) idle.
The intent is to lower power consumption to ride-out
transient electrical and thermal emergencies,
rather than powering off the server.
On platforms that can save more power/performance via P-states,
the platform will first exhaust P-states before forcing idle.
However, the relative benefit of P-states vs. idle states
is platform dependent, and thus this driver need not know
or care about it.
This driver does not use the kernel's CPU hot-plug mechanism
because after the transient emergency is over, the system must
be returned to its normal state, and hotplug would permanently
break both cpusets and binding.
So to force idle, the driver creates a power saving thread.
The scheduler will migrate the thread to the preferred CPU.
The thread has max priority and has SCHED_RR policy,
so it can occupy one CPU. To save power, the thread will
invoke the deep C-state entry instructions.
To avoid starvation, the thread will sleep 5% of the time
time for every second (current RT scheduler has threshold
to avoid starvation, but if other CPUs are idle,
the CPU can borrow CPU timer from other,
which makes the mechanism not work here)
Vaidyanathan Srinivasan has proposed scheduler enhancements
to allow injecting idle time into the system. This driver doesn't
depend on those enhancements, but could cut over to them
when they are available.
Peter Z. does not favor upstreaming this driver until
the those scheduler enhancements are in place. However,
we favor upstreaming this driver now because it is useful
now, and can be enhanced over time.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
NACKed-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2009-07-28 06:11:02 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_THERMAL
|
|
|
|
tristate "Thermal Zone"
|
|
|
|
depends on ACPI_PROCESSOR
|
2008-01-17 15:51:11 +08:00
|
|
|
select THERMAL
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver supports ACPI thermal zones. Most mobile and
|
2005-04-17 06:20:36 +08:00
|
|
|
some desktop systems support ACPI thermal zones. It is HIGHLY
|
|
|
|
recommended that this option be enabled, as your processor(s)
|
|
|
|
may be damaged without it.
|
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called thermal.
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_NUMA
|
|
|
|
bool "NUMA support"
|
|
|
|
depends on NUMA
|
2006-06-23 17:03:19 +08:00
|
|
|
depends on (X86 || IA64)
|
2005-04-17 06:20:36 +08:00
|
|
|
default y if IA64_GENERIC || IA64_SGI_SN2
|
|
|
|
|
2008-02-23 03:25:04 +08:00
|
|
|
config ACPI_CUSTOM_DSDT_FILE
|
|
|
|
string "Custom DSDT Table file to include"
|
|
|
|
default ""
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on !STANDALONE
|
|
|
|
help
|
2008-02-07 08:28:02 +08:00
|
|
|
This option supports a custom DSDT by linking it into the kernel.
|
|
|
|
See Documentation/acpi/dsdt-override.txt
|
|
|
|
|
2006-03-25 01:23:14 +08:00
|
|
|
Enter the full path name to the file which includes the AmlCode
|
|
|
|
declaration.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2008-02-23 03:25:04 +08:00
|
|
|
If unsure, don't enter a file name.
|
|
|
|
|
|
|
|
config ACPI_CUSTOM_DSDT
|
|
|
|
bool
|
|
|
|
default ACPI_CUSTOM_DSDT_FILE != ""
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_BLACKLIST_YEAR
|
2006-02-26 11:18:43 +08:00
|
|
|
int "Disable ACPI for systems before Jan 1st this year" if X86_32
|
2005-04-17 06:20:36 +08:00
|
|
|
default 0
|
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
Enter a 4-digit year, e.g., 2001, to disable ACPI by default
|
2005-04-17 06:20:36 +08:00
|
|
|
on platforms with DMI BIOS date before January 1st that year.
|
|
|
|
"acpi=force" can be used to override this mechanism.
|
|
|
|
|
|
|
|
Enter 0 to disable this mechanism and allow ACPI to
|
|
|
|
run by default no matter what the year. (default)
|
|
|
|
|
|
|
|
config ACPI_DEBUG
|
|
|
|
bool "Debug Statements"
|
|
|
|
default n
|
|
|
|
help
|
2008-11-08 07:58:05 +08:00
|
|
|
The ACPI subsystem can produce debug output. Saying Y enables this
|
|
|
|
output and increases the kernel size by around 50K.
|
|
|
|
|
|
|
|
Use the acpi.debug_layer and acpi.debug_level kernel command-line
|
|
|
|
parameters documented in Documentation/acpi/debug.txt and
|
|
|
|
Documentation/kernel-parameters.txt to control the type and
|
|
|
|
amount of debug output.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-05-31 23:20:39 +08:00
|
|
|
config ACPI_DEBUG_FUNC_TRACE
|
|
|
|
bool "Additionally enable ACPI function tracing"
|
|
|
|
default n
|
|
|
|
depends on ACPI_DEBUG
|
|
|
|
help
|
|
|
|
ACPI Debug Statements slow down ACPI processing. Function trace
|
|
|
|
is about half of the penalty and is rarely useful.
|
|
|
|
|
2008-06-11 05:30:42 +08:00
|
|
|
config ACPI_PCI_SLOT
|
|
|
|
tristate "PCI slot detection driver"
|
2009-06-18 09:03:57 +08:00
|
|
|
depends on SYSFS
|
2008-06-11 05:30:42 +08:00
|
|
|
default n
|
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver creates entries in /sys/bus/pci/slots/ for all PCI
|
|
|
|
slots in the system. This can help correlate PCI bus addresses,
|
|
|
|
i.e., segment/bus/device/function tuples, with physical slots in
|
|
|
|
the system. If you are unsure, say N.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called pci_slot.
|
2008-06-11 05:30:42 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config X86_PM_TIMER
|
2006-02-26 11:18:37 +08:00
|
|
|
bool "Power Management Timer Support" if EMBEDDED
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on X86
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
The Power Management Timer is available on all ACPI-capable,
|
|
|
|
in most cases even if ACPI is unusable or blacklisted.
|
|
|
|
|
2006-10-04 04:24:43 +08:00
|
|
|
This timing source is not affected by power management features
|
2005-04-17 06:20:36 +08:00
|
|
|
like aggressive processor idling, throttling, frequency and/or
|
|
|
|
voltage scaling, unlike the commonly used Time Stamp Counter
|
|
|
|
(TSC) timing source.
|
|
|
|
|
2006-02-26 11:18:37 +08:00
|
|
|
You should nearly always say Y here because many modern
|
|
|
|
systems require this timer.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
config ACPI_CONTAINER
|
2009-02-20 05:45:47 +08:00
|
|
|
tristate "Container and Module Devices (EXPERIMENTAL)"
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on EXPERIMENTAL
|
|
|
|
default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU || ACPI_HOTPLUG_IO)
|
2009-02-20 05:45:47 +08:00
|
|
|
help
|
|
|
|
This driver supports ACPI Container and Module devices (IDs
|
|
|
|
ACPI0004, PNP0A05, and PNP0A06).
|
2005-03-02 13:00:00 +08:00
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
This helps support hotplug of nodes, CPUs, and memory.
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called container.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
config ACPI_HOTPLUG_MEMORY
|
|
|
|
tristate "Memory Hotplug"
|
2006-06-27 17:53:30 +08:00
|
|
|
depends on MEMORY_HOTPLUG
|
2005-04-17 06:20:36 +08:00
|
|
|
default n
|
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver supports ACPI memory hotplug. The driver
|
|
|
|
fields notifications on ACPI memory devices (PNP0C80),
|
|
|
|
which represent memory ranges that may be onlined or
|
|
|
|
offlined during runtime.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
If your hardware and firmware do not support adding or
|
|
|
|
removing memory devices at runtime, you need not enable
|
|
|
|
this driver.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the module will be called acpi_memhotplug.
|
2006-07-01 23:36:54 +08:00
|
|
|
|
|
|
|
config ACPI_SBS
|
2007-09-26 23:43:48 +08:00
|
|
|
tristate "Smart Battery System"
|
2007-03-19 22:45:50 +08:00
|
|
|
depends on X86
|
2006-07-01 23:36:54 +08:00
|
|
|
help
|
2009-02-20 05:45:47 +08:00
|
|
|
This driver supports the Smart Battery System, another
|
2007-09-26 23:43:48 +08:00
|
|
|
type of access to battery information, found on some laptops.
|
2006-07-01 23:36:54 +08:00
|
|
|
|
2009-02-20 05:45:47 +08:00
|
|
|
To compile this driver as a module, choose M here:
|
|
|
|
the modules will be called sbs and sbshc.
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
endif # ACPI
|