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"
|
2007-02-03 10:05:04 +08:00
|
|
|
depends on !X86_NUMAQ
|
2005-04-17 06:20:36 +08:00
|
|
|
depends on !X86_VISWS
|
|
|
|
|
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
|
2005-04-17 06:20:36 +08:00
|
|
|
default y
|
|
|
|
|
---help---
|
|
|
|
|
Advanced Configuration and Power Interface (ACPI) support for
|
|
|
|
|
Linux requires an ACPI compliant platform (hardware/firmware),
|
|
|
|
|
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
|
|
|
|
|
are configured, whichever is loaded first shall be used.
|
|
|
|
|
|
|
|
|
|
The ACPI SourceForge project contains the latest source code,
|
|
|
|
|
documentation, tools, mailing list subscription, and other
|
|
|
|
|
information. This project is available at:
|
|
|
|
|
<http://sourceforge.net/projects/acpi>
|
|
|
|
|
|
|
|
|
|
Linux support for ACPI is based on Intel Corporation's ACPI
|
|
|
|
|
Component Architecture (ACPI CA). For more information see:
|
|
|
|
|
<http://developer.intel.com/technology/iapc/acpi>
|
|
|
|
|
|
|
|
|
|
ACPI is an open industry specification co-developed by Compaq,
|
|
|
|
|
Intel, Microsoft, Phoenix, and Toshiba. The specification is
|
|
|
|
|
available at:
|
|
|
|
|
<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
|
|
|
|
|
depends on PM_SLEEP
|
|
|
|
|
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
|
2007-01-29 11:02:30 +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)
|
2007-07-24 13:50:46 +08:00
|
|
|
/proc/acpi/info (/sys/modules/acpi/parameters/acpica_version)
|
|
|
|
|
/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)
|
|
|
|
|
|
|
|
|
|
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/
|
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
|
|
|
|
|
---help---
|
|
|
|
|
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/
|
|
|
|
|
|
2008-01-02 03:27:24 +08:00
|
|
|
config ACPI_SYSFS_POWER
|
|
|
|
|
bool "Future power /sys interface"
|
|
|
|
|
select POWER_SUPPLY
|
|
|
|
|
default y
|
|
|
|
|
---help---
|
|
|
|
|
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
|
2007-08-24 03:20:26 +08:00
|
|
|
---help---
|
|
|
|
|
A user-space daemon, acpi, typically read /proc/acpi/event
|
|
|
|
|
and handled all ACPI sub-system generated events.
|
|
|
|
|
|
|
|
|
|
These events are now delivered to user-space via
|
|
|
|
|
either the input layer, or as netlink events.
|
|
|
|
|
|
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
|
|
|
|
|
This driver adds support for the AC Adapter object, which indicates
|
2005-08-26 00:22:04 +08:00
|
|
|
whether a system is on AC, or not. If you have a system that can
|
|
|
|
|
switch between A/C and battery, say Y.
|
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.
|
|
|
|
|
|
|
|
|
|
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
|
2005-08-26 00:22:04 +08:00
|
|
|
This driver handles events on the power, sleep and lid buttons.
|
|
|
|
|
A daemon reads /proc/acpi/event and perform user-defined actions
|
|
|
|
|
such as shutting down the system. This is necessary for
|
|
|
|
|
software controlled poweroff.
|
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
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
This driver implement the ACPI Extensions For Display Adapters
|
|
|
|
|
for integrated graphics devices on motherboard, as specified in
|
|
|
|
|
ACPI 2.0 Specification, Appendix B, allowing to perform some basic
|
|
|
|
|
control like defining the video POST device, retrieving EDID information
|
|
|
|
|
or to setup a video output, etc.
|
|
|
|
|
Note that this is an ref. implementation only. It may or may not work
|
|
|
|
|
for your integrated video device.
|
|
|
|
|
|
|
|
|
|
config ACPI_FAN
|
|
|
|
|
tristate "Fan"
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
This driver adds support for ACPI fan devices, allowing user-mode
|
|
|
|
|
applications to perform basic fan control (on, off, status).
|
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
config ACPI_DOCK
|
|
|
|
|
tristate "Dock"
|
2006-07-10 10:09:57 +08:00
|
|
|
depends on EXPERIMENTAL
|
2006-07-10 05:22:28 +08:00
|
|
|
help
|
|
|
|
|
This driver adds support for ACPI controlled docking stations
|
|
|
|
|
|
2006-10-21 05:30:25 +08:00
|
|
|
config ACPI_BAY
|
2007-02-03 11:39:16 +08:00
|
|
|
tristate "Removable Drive Bay (EXPERIMENTAL)"
|
2006-10-21 05:30:25 +08:00
|
|
|
depends on EXPERIMENTAL
|
2007-03-01 12:13:17 +08:00
|
|
|
depends on ACPI_DOCK
|
2006-10-21 05:30:25 +08:00
|
|
|
help
|
|
|
|
|
This driver adds support for ACPI controlled removable drive
|
|
|
|
|
bays such as the IBM ultrabay or the Dell Module Bay.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_PROCESSOR
|
|
|
|
|
tristate "Processor"
|
2005-08-26 00:22:04 +08:00
|
|
|
default y
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
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
|
|
|
|
|
Performance-state drivers.
|
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
|
|
|
|
|
|
|
|
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
|
|
|
|
|
This driver adds support for ACPI thermal zones. Most mobile and
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
ACPI: WMI: Add ACPI-WMI mapping driver
The following is an implementation of the Windows Management
Instrumentation (WMI) ACPI interface mapper (PNP0C14).
What it does:
Parses the _WDG method and exports functions to process WMI method calls,
data block query/ set commands (both based on GUID) and does basic event
handling.
How: WMI presents an in kernel interface here (essentially, a minimal
wrapper around ACPI)
(const char *guid assume the 36 character ASCII representation of
a GUID - e.g. 67C3371D-95A3-4C37-BB61-DD47B491DAAB)
wmi_evaluate_method(const char *guid, u8 instance, u32 method_id,
const struct acpi_buffer *in, struct acpi_buffer *out)
wmi_query_block(const char *guid, u8 instance,
struct acpi_buffer *out)
wmi_set_block(const char *guid, u38 instance,
const struct acpi_buffer *in)
wmi_install_notify_handler(acpi_notify_handler handler);
wmi_remove_notify_handler(void);
wmi_get_event_data(u32 event, struct acpi_buffer *out)
wmi_has_guid(const char guid*)
wmi_has_guid() is a helper function to find if a GUID exists or not on the
system (a quick and easy way for WMI dependant drivers to see if the
the method/ block they want exists, since GUIDs are supposed to be unique).
Event handling - allow a WMI based driver to register a notifier handler
for each GUID with WMI. When a notification is sent to a GUID in WMI, the
handler registered with WMI is then called (it is left to the caller to
ask for the WMI event data associated with the GUID, if needed).
What it won't do:
Unicode - The MS article[1] calls for converting between ASCII and Unicode (or
vice versa) if a GUID is marked as "string". This is left up to the calling
driver.
Handle a MOF[1] - the WMI mapper just exports methods, data and events to
userspace. MOF handling is down to userspace.
Userspace interface - this will be added later.
[1] http://www.microsoft.com/whdc/system/pnppwr/wmi/wmi-acpi.mspx
===
ChangeLog
==
v1 (2007-10-02):
* Initial release
v2 (2007-10-05):
* Cleaned up code - split up super "wmi_evaluate_block" -> each external
symbol now handles its own ACPI calls, rather than handing off to
a "super" method (and in turn, is a lot simpler to read)
* Added a find_guid() symbol - return true if a given GUID exists on
the system
* wmi_* functions now return type acpi_status (since they are just
fancy wrappers around acpi_evaluate_object())
* Removed extra debug code
v3 (2007-10-27)
* More code clean up - now passes checkpatch.pl
* Change data block calls - ref MS spec, method ID is not required for
them, so drop it from the function parameters.
* Const'ify guid in the function call parameters.
* Fix _WDG buffer handling - copy the data to our own private structure.
* Change WMI from tristate to bool - otherwise the external functions are
not exported in linux/acpi.h if you try to build WMI as a module.
* Fix more flag comparisons.
* Add a maintainers entry - since I wrote this, I should take the blame
for it.
v4 (2007-10-30)
* Add missing brace from after fixing checkpatch errors.
* Rewrote event handling - allow external drivers to register with WMI to
handle WMI events
* Clean up flags and sanitise flag handling
v5 (2007-11-03)
* Add sysfs interface for userspace. Export events over netlink again.
* Remove module left overs, fully convert to built-in driver.
* Tweak in-kernel API to use u8 for instance, since this is what the GUID
blocks use (so instance cannot be greater than u8).
* Export wmi_get_event_data() for in kernel WMI drivers.
v6 (2007-11-07)
* Split out userspace into a different patch
v7 (2007-11-20)
* Fix driver to handle multiple PNP0C14 devices - store all GUIDs using
the kernel's built in list functions, and just keep adding to the list
every time we handle a PNP0C14 devices - GUIDs will always be unique,
and WMI callers do not know or care about different devices.
* Change WMI event handler registration to use its' own event handling
struct; we should not pass an acpi_handle down to any WMI based drivers
- they should be able to function with only the calls provided in WMI.
* Update my e-mail address
v8 (2007-11-28)
* Convert back to a module.
* Update Kconfig to default to building as a module.
* Remove an erroneous printk.
* Simply comments for string flag (since we now leave the handling to the
caller).
v9 (2007-12-07)
* Add back missing MODULE_DEVICE_TABLE for autoloading
* Checkpatch fixes
v10 (2007-12-12)
* Workaround broken GUIDs declared expensive without a WCxx method.
* Minor cleanups
v11 (2007-12-17)
* More fixing for broken GUIDs declared expensive without a WCxx method.
* Add basic EmbeddedControl region handling.
v12 (2007-12-18)
* Changed EC region handling code, as per Alexey's comments.
v13 (2007-12-27)
* Changed event handling so that we can have one event handler registered
per GUID, as per Matthew Garrett's suggestion.
v14 (2008-01-12)
* Remove ACPI debug statements
v15 (2008-02-01)
* Replace two remaining 'x == NULL' type tests with '!x'
v16 (2008-02-05)
* Change MAINTAINERS entry, as I am not, and never have been, paid to work
on WMI
* Remove 'default' line from Kconfig
Signed-off-by: Carlos Corbacho <carlos@strangeworlds.co.uk>
CC: Matthew Garrett <mjg59@srcf.ucam.org>
CC: Alexey Starikovskiy <aystarik@gmail.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-02-05 10:17:04 +08:00
|
|
|
config ACPI_WMI
|
|
|
|
|
tristate "WMI (EXPERIMENTAL)"
|
2008-02-08 05:18:24 +08:00
|
|
|
depends on X86
|
ACPI: WMI: Add ACPI-WMI mapping driver
The following is an implementation of the Windows Management
Instrumentation (WMI) ACPI interface mapper (PNP0C14).
What it does:
Parses the _WDG method and exports functions to process WMI method calls,
data block query/ set commands (both based on GUID) and does basic event
handling.
How: WMI presents an in kernel interface here (essentially, a minimal
wrapper around ACPI)
(const char *guid assume the 36 character ASCII representation of
a GUID - e.g. 67C3371D-95A3-4C37-BB61-DD47B491DAAB)
wmi_evaluate_method(const char *guid, u8 instance, u32 method_id,
const struct acpi_buffer *in, struct acpi_buffer *out)
wmi_query_block(const char *guid, u8 instance,
struct acpi_buffer *out)
wmi_set_block(const char *guid, u38 instance,
const struct acpi_buffer *in)
wmi_install_notify_handler(acpi_notify_handler handler);
wmi_remove_notify_handler(void);
wmi_get_event_data(u32 event, struct acpi_buffer *out)
wmi_has_guid(const char guid*)
wmi_has_guid() is a helper function to find if a GUID exists or not on the
system (a quick and easy way for WMI dependant drivers to see if the
the method/ block they want exists, since GUIDs are supposed to be unique).
Event handling - allow a WMI based driver to register a notifier handler
for each GUID with WMI. When a notification is sent to a GUID in WMI, the
handler registered with WMI is then called (it is left to the caller to
ask for the WMI event data associated with the GUID, if needed).
What it won't do:
Unicode - The MS article[1] calls for converting between ASCII and Unicode (or
vice versa) if a GUID is marked as "string". This is left up to the calling
driver.
Handle a MOF[1] - the WMI mapper just exports methods, data and events to
userspace. MOF handling is down to userspace.
Userspace interface - this will be added later.
[1] http://www.microsoft.com/whdc/system/pnppwr/wmi/wmi-acpi.mspx
===
ChangeLog
==
v1 (2007-10-02):
* Initial release
v2 (2007-10-05):
* Cleaned up code - split up super "wmi_evaluate_block" -> each external
symbol now handles its own ACPI calls, rather than handing off to
a "super" method (and in turn, is a lot simpler to read)
* Added a find_guid() symbol - return true if a given GUID exists on
the system
* wmi_* functions now return type acpi_status (since they are just
fancy wrappers around acpi_evaluate_object())
* Removed extra debug code
v3 (2007-10-27)
* More code clean up - now passes checkpatch.pl
* Change data block calls - ref MS spec, method ID is not required for
them, so drop it from the function parameters.
* Const'ify guid in the function call parameters.
* Fix _WDG buffer handling - copy the data to our own private structure.
* Change WMI from tristate to bool - otherwise the external functions are
not exported in linux/acpi.h if you try to build WMI as a module.
* Fix more flag comparisons.
* Add a maintainers entry - since I wrote this, I should take the blame
for it.
v4 (2007-10-30)
* Add missing brace from after fixing checkpatch errors.
* Rewrote event handling - allow external drivers to register with WMI to
handle WMI events
* Clean up flags and sanitise flag handling
v5 (2007-11-03)
* Add sysfs interface for userspace. Export events over netlink again.
* Remove module left overs, fully convert to built-in driver.
* Tweak in-kernel API to use u8 for instance, since this is what the GUID
blocks use (so instance cannot be greater than u8).
* Export wmi_get_event_data() for in kernel WMI drivers.
v6 (2007-11-07)
* Split out userspace into a different patch
v7 (2007-11-20)
* Fix driver to handle multiple PNP0C14 devices - store all GUIDs using
the kernel's built in list functions, and just keep adding to the list
every time we handle a PNP0C14 devices - GUIDs will always be unique,
and WMI callers do not know or care about different devices.
* Change WMI event handler registration to use its' own event handling
struct; we should not pass an acpi_handle down to any WMI based drivers
- they should be able to function with only the calls provided in WMI.
* Update my e-mail address
v8 (2007-11-28)
* Convert back to a module.
* Update Kconfig to default to building as a module.
* Remove an erroneous printk.
* Simply comments for string flag (since we now leave the handling to the
caller).
v9 (2007-12-07)
* Add back missing MODULE_DEVICE_TABLE for autoloading
* Checkpatch fixes
v10 (2007-12-12)
* Workaround broken GUIDs declared expensive without a WCxx method.
* Minor cleanups
v11 (2007-12-17)
* More fixing for broken GUIDs declared expensive without a WCxx method.
* Add basic EmbeddedControl region handling.
v12 (2007-12-18)
* Changed EC region handling code, as per Alexey's comments.
v13 (2007-12-27)
* Changed event handling so that we can have one event handler registered
per GUID, as per Matthew Garrett's suggestion.
v14 (2008-01-12)
* Remove ACPI debug statements
v15 (2008-02-01)
* Replace two remaining 'x == NULL' type tests with '!x'
v16 (2008-02-05)
* Change MAINTAINERS entry, as I am not, and never have been, paid to work
on WMI
* Remove 'default' line from Kconfig
Signed-off-by: Carlos Corbacho <carlos@strangeworlds.co.uk>
CC: Matthew Garrett <mjg59@srcf.ucam.org>
CC: Alexey Starikovskiy <aystarik@gmail.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-02-05 10:17:04 +08:00
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
help
|
2008-02-08 13:36:49 +08:00
|
|
|
This driver adds support for the ACPI-WMI (Windows Management
|
|
|
|
|
Instrumentation) mapper device (PNP0C14) found on some systems.
|
ACPI: WMI: Add ACPI-WMI mapping driver
The following is an implementation of the Windows Management
Instrumentation (WMI) ACPI interface mapper (PNP0C14).
What it does:
Parses the _WDG method and exports functions to process WMI method calls,
data block query/ set commands (both based on GUID) and does basic event
handling.
How: WMI presents an in kernel interface here (essentially, a minimal
wrapper around ACPI)
(const char *guid assume the 36 character ASCII representation of
a GUID - e.g. 67C3371D-95A3-4C37-BB61-DD47B491DAAB)
wmi_evaluate_method(const char *guid, u8 instance, u32 method_id,
const struct acpi_buffer *in, struct acpi_buffer *out)
wmi_query_block(const char *guid, u8 instance,
struct acpi_buffer *out)
wmi_set_block(const char *guid, u38 instance,
const struct acpi_buffer *in)
wmi_install_notify_handler(acpi_notify_handler handler);
wmi_remove_notify_handler(void);
wmi_get_event_data(u32 event, struct acpi_buffer *out)
wmi_has_guid(const char guid*)
wmi_has_guid() is a helper function to find if a GUID exists or not on the
system (a quick and easy way for WMI dependant drivers to see if the
the method/ block they want exists, since GUIDs are supposed to be unique).
Event handling - allow a WMI based driver to register a notifier handler
for each GUID with WMI. When a notification is sent to a GUID in WMI, the
handler registered with WMI is then called (it is left to the caller to
ask for the WMI event data associated with the GUID, if needed).
What it won't do:
Unicode - The MS article[1] calls for converting between ASCII and Unicode (or
vice versa) if a GUID is marked as "string". This is left up to the calling
driver.
Handle a MOF[1] - the WMI mapper just exports methods, data and events to
userspace. MOF handling is down to userspace.
Userspace interface - this will be added later.
[1] http://www.microsoft.com/whdc/system/pnppwr/wmi/wmi-acpi.mspx
===
ChangeLog
==
v1 (2007-10-02):
* Initial release
v2 (2007-10-05):
* Cleaned up code - split up super "wmi_evaluate_block" -> each external
symbol now handles its own ACPI calls, rather than handing off to
a "super" method (and in turn, is a lot simpler to read)
* Added a find_guid() symbol - return true if a given GUID exists on
the system
* wmi_* functions now return type acpi_status (since they are just
fancy wrappers around acpi_evaluate_object())
* Removed extra debug code
v3 (2007-10-27)
* More code clean up - now passes checkpatch.pl
* Change data block calls - ref MS spec, method ID is not required for
them, so drop it from the function parameters.
* Const'ify guid in the function call parameters.
* Fix _WDG buffer handling - copy the data to our own private structure.
* Change WMI from tristate to bool - otherwise the external functions are
not exported in linux/acpi.h if you try to build WMI as a module.
* Fix more flag comparisons.
* Add a maintainers entry - since I wrote this, I should take the blame
for it.
v4 (2007-10-30)
* Add missing brace from after fixing checkpatch errors.
* Rewrote event handling - allow external drivers to register with WMI to
handle WMI events
* Clean up flags and sanitise flag handling
v5 (2007-11-03)
* Add sysfs interface for userspace. Export events over netlink again.
* Remove module left overs, fully convert to built-in driver.
* Tweak in-kernel API to use u8 for instance, since this is what the GUID
blocks use (so instance cannot be greater than u8).
* Export wmi_get_event_data() for in kernel WMI drivers.
v6 (2007-11-07)
* Split out userspace into a different patch
v7 (2007-11-20)
* Fix driver to handle multiple PNP0C14 devices - store all GUIDs using
the kernel's built in list functions, and just keep adding to the list
every time we handle a PNP0C14 devices - GUIDs will always be unique,
and WMI callers do not know or care about different devices.
* Change WMI event handler registration to use its' own event handling
struct; we should not pass an acpi_handle down to any WMI based drivers
- they should be able to function with only the calls provided in WMI.
* Update my e-mail address
v8 (2007-11-28)
* Convert back to a module.
* Update Kconfig to default to building as a module.
* Remove an erroneous printk.
* Simply comments for string flag (since we now leave the handling to the
caller).
v9 (2007-12-07)
* Add back missing MODULE_DEVICE_TABLE for autoloading
* Checkpatch fixes
v10 (2007-12-12)
* Workaround broken GUIDs declared expensive without a WCxx method.
* Minor cleanups
v11 (2007-12-17)
* More fixing for broken GUIDs declared expensive without a WCxx method.
* Add basic EmbeddedControl region handling.
v12 (2007-12-18)
* Changed EC region handling code, as per Alexey's comments.
v13 (2007-12-27)
* Changed event handling so that we can have one event handler registered
per GUID, as per Matthew Garrett's suggestion.
v14 (2008-01-12)
* Remove ACPI debug statements
v15 (2008-02-01)
* Replace two remaining 'x == NULL' type tests with '!x'
v16 (2008-02-05)
* Change MAINTAINERS entry, as I am not, and never have been, paid to work
on WMI
* Remove 'default' line from Kconfig
Signed-off-by: Carlos Corbacho <carlos@strangeworlds.co.uk>
CC: Matthew Garrett <mjg59@srcf.ucam.org>
CC: Alexey Starikovskiy <aystarik@gmail.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-02-05 10:17:04 +08:00
|
|
|
|
2008-02-08 13:36:49 +08:00
|
|
|
ACPI-WMI is a proprietary extension to ACPI to expose parts of the
|
|
|
|
|
ACPI firmware to userspace - this is done through various vendor
|
|
|
|
|
defined methods and data blocks in a PNP0C14 device, which are then
|
|
|
|
|
made available for userspace to call.
|
|
|
|
|
|
|
|
|
|
The implementation of this in Linux currently only exposes this to
|
|
|
|
|
other kernel space drivers.
|
|
|
|
|
|
|
|
|
|
This driver is a required dependency to build the firmware specific
|
|
|
|
|
drivers needed on many machines, including Acer and HP laptops.
|
|
|
|
|
|
|
|
|
|
It is safe to enable this driver even if your DSDT doesn't define
|
|
|
|
|
any ACPI-WMI devices.
|
ACPI: WMI: Add ACPI-WMI mapping driver
The following is an implementation of the Windows Management
Instrumentation (WMI) ACPI interface mapper (PNP0C14).
What it does:
Parses the _WDG method and exports functions to process WMI method calls,
data block query/ set commands (both based on GUID) and does basic event
handling.
How: WMI presents an in kernel interface here (essentially, a minimal
wrapper around ACPI)
(const char *guid assume the 36 character ASCII representation of
a GUID - e.g. 67C3371D-95A3-4C37-BB61-DD47B491DAAB)
wmi_evaluate_method(const char *guid, u8 instance, u32 method_id,
const struct acpi_buffer *in, struct acpi_buffer *out)
wmi_query_block(const char *guid, u8 instance,
struct acpi_buffer *out)
wmi_set_block(const char *guid, u38 instance,
const struct acpi_buffer *in)
wmi_install_notify_handler(acpi_notify_handler handler);
wmi_remove_notify_handler(void);
wmi_get_event_data(u32 event, struct acpi_buffer *out)
wmi_has_guid(const char guid*)
wmi_has_guid() is a helper function to find if a GUID exists or not on the
system (a quick and easy way for WMI dependant drivers to see if the
the method/ block they want exists, since GUIDs are supposed to be unique).
Event handling - allow a WMI based driver to register a notifier handler
for each GUID with WMI. When a notification is sent to a GUID in WMI, the
handler registered with WMI is then called (it is left to the caller to
ask for the WMI event data associated with the GUID, if needed).
What it won't do:
Unicode - The MS article[1] calls for converting between ASCII and Unicode (or
vice versa) if a GUID is marked as "string". This is left up to the calling
driver.
Handle a MOF[1] - the WMI mapper just exports methods, data and events to
userspace. MOF handling is down to userspace.
Userspace interface - this will be added later.
[1] http://www.microsoft.com/whdc/system/pnppwr/wmi/wmi-acpi.mspx
===
ChangeLog
==
v1 (2007-10-02):
* Initial release
v2 (2007-10-05):
* Cleaned up code - split up super "wmi_evaluate_block" -> each external
symbol now handles its own ACPI calls, rather than handing off to
a "super" method (and in turn, is a lot simpler to read)
* Added a find_guid() symbol - return true if a given GUID exists on
the system
* wmi_* functions now return type acpi_status (since they are just
fancy wrappers around acpi_evaluate_object())
* Removed extra debug code
v3 (2007-10-27)
* More code clean up - now passes checkpatch.pl
* Change data block calls - ref MS spec, method ID is not required for
them, so drop it from the function parameters.
* Const'ify guid in the function call parameters.
* Fix _WDG buffer handling - copy the data to our own private structure.
* Change WMI from tristate to bool - otherwise the external functions are
not exported in linux/acpi.h if you try to build WMI as a module.
* Fix more flag comparisons.
* Add a maintainers entry - since I wrote this, I should take the blame
for it.
v4 (2007-10-30)
* Add missing brace from after fixing checkpatch errors.
* Rewrote event handling - allow external drivers to register with WMI to
handle WMI events
* Clean up flags and sanitise flag handling
v5 (2007-11-03)
* Add sysfs interface for userspace. Export events over netlink again.
* Remove module left overs, fully convert to built-in driver.
* Tweak in-kernel API to use u8 for instance, since this is what the GUID
blocks use (so instance cannot be greater than u8).
* Export wmi_get_event_data() for in kernel WMI drivers.
v6 (2007-11-07)
* Split out userspace into a different patch
v7 (2007-11-20)
* Fix driver to handle multiple PNP0C14 devices - store all GUIDs using
the kernel's built in list functions, and just keep adding to the list
every time we handle a PNP0C14 devices - GUIDs will always be unique,
and WMI callers do not know or care about different devices.
* Change WMI event handler registration to use its' own event handling
struct; we should not pass an acpi_handle down to any WMI based drivers
- they should be able to function with only the calls provided in WMI.
* Update my e-mail address
v8 (2007-11-28)
* Convert back to a module.
* Update Kconfig to default to building as a module.
* Remove an erroneous printk.
* Simply comments for string flag (since we now leave the handling to the
caller).
v9 (2007-12-07)
* Add back missing MODULE_DEVICE_TABLE for autoloading
* Checkpatch fixes
v10 (2007-12-12)
* Workaround broken GUIDs declared expensive without a WCxx method.
* Minor cleanups
v11 (2007-12-17)
* More fixing for broken GUIDs declared expensive without a WCxx method.
* Add basic EmbeddedControl region handling.
v12 (2007-12-18)
* Changed EC region handling code, as per Alexey's comments.
v13 (2007-12-27)
* Changed event handling so that we can have one event handler registered
per GUID, as per Matthew Garrett's suggestion.
v14 (2008-01-12)
* Remove ACPI debug statements
v15 (2008-02-01)
* Replace two remaining 'x == NULL' type tests with '!x'
v16 (2008-02-05)
* Change MAINTAINERS entry, as I am not, and never have been, paid to work
on WMI
* Remove 'default' line from Kconfig
Signed-off-by: Carlos Corbacho <carlos@strangeworlds.co.uk>
CC: Matthew Garrett <mjg59@srcf.ucam.org>
CC: Alexey Starikovskiy <aystarik@gmail.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-02-05 10:17:04 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_ASUS
|
|
|
|
|
tristate "ASUS/Medion Laptop Extras"
|
|
|
|
|
depends on X86
|
2006-10-21 05:30:29 +08:00
|
|
|
select BACKLIGHT_CLASS_DEVICE
|
2005-04-17 06:20:36 +08:00
|
|
|
---help---
|
|
|
|
|
This driver provides support for extra features of ACPI-compatible
|
|
|
|
|
ASUS laptops. As some of Medion laptops are made by ASUS, it may also
|
|
|
|
|
support some Medion laptops (such as 9675 for example). It makes all
|
|
|
|
|
the extra buttons generate standard ACPI events that go through
|
|
|
|
|
/proc/acpi/events, and (on some models) adds support for changing the
|
|
|
|
|
display brightness and output, switching the LCD backlight on and off,
|
|
|
|
|
and most importantly, allows you to blink those fancy LEDs intended
|
|
|
|
|
for reporting mail and wireless status.
|
|
|
|
|
|
|
|
|
|
Note: display switching code is currently considered EXPERIMENTAL,
|
|
|
|
|
toying with these values may even lock your machine.
|
2007-01-26 21:04:30 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
All settings are changed via /proc/acpi/asus directory entries. Owner
|
|
|
|
|
and group for these entries can be set with asus_uid and asus_gid
|
|
|
|
|
parameters.
|
2007-01-26 21:04:30 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
More information and a userspace daemon for handling the extra buttons
|
|
|
|
|
at <http://sourceforge.net/projects/acpi4asus/>.
|
2007-01-26 21:04:30 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
If you have an ACPI-compatible ASUS laptop, say Y or M here. This
|
|
|
|
|
driver is still under development, so if your laptop is unsupported or
|
|
|
|
|
something works not quite as expected, please use the mailing list
|
2007-01-26 21:04:30 +08:00
|
|
|
available on the above page (acpi4asus-user@lists.sourceforge.net).
|
|
|
|
|
|
|
|
|
|
NOTE: This driver is deprecated and will probably be removed soon,
|
|
|
|
|
use asus-laptop instead.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_TOSHIBA
|
|
|
|
|
tristate "Toshiba Laptop Extras"
|
|
|
|
|
depends on X86
|
2006-10-21 05:30:29 +08:00
|
|
|
select BACKLIGHT_CLASS_DEVICE
|
2005-04-17 06:20:36 +08:00
|
|
|
---help---
|
|
|
|
|
This driver adds support for access to certain system settings
|
|
|
|
|
on "legacy free" Toshiba laptops. These laptops can be recognized by
|
|
|
|
|
their lack of a BIOS setup menu and APM support.
|
|
|
|
|
|
|
|
|
|
On these machines, all system configuration is handled through the
|
|
|
|
|
ACPI. This driver is required for access to controls not covered
|
|
|
|
|
by the general ACPI drivers, such as LCD brightness, video output,
|
|
|
|
|
etc.
|
|
|
|
|
|
|
|
|
|
This driver differs from the non-ACPI Toshiba laptop driver (located
|
|
|
|
|
under "Processor type and features") in several aspects.
|
|
|
|
|
Configuration is accessed by reading and writing text files in the
|
|
|
|
|
/proc tree instead of by program interface to /dev. Furthermore, no
|
|
|
|
|
power management functions are exposed, as those are handled by the
|
|
|
|
|
general ACPI drivers.
|
|
|
|
|
|
|
|
|
|
More information about this driver is available at
|
|
|
|
|
<http://memebeam.org/toys/ToshibaAcpiDriver>.
|
|
|
|
|
|
|
|
|
|
If you have a legacy free Toshiba laptop (such as the Libretto L1
|
|
|
|
|
series), say Y.
|
|
|
|
|
|
|
|
|
|
config ACPI_CUSTOM_DSDT
|
|
|
|
|
bool "Include Custom DSDT"
|
|
|
|
|
depends on !STANDALONE
|
|
|
|
|
default n
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config ACPI_CUSTOM_DSDT_FILE
|
|
|
|
|
string "Custom DSDT Table file to include"
|
|
|
|
|
depends on ACPI_CUSTOM_DSDT
|
|
|
|
|
default ""
|
|
|
|
|
help
|
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-05 07:04:06 +08:00
|
|
|
config ACPI_CUSTOM_DSDT_INITRD
|
|
|
|
|
bool "Read Custom DSDT from initramfs"
|
|
|
|
|
depends on BLK_DEV_INITRD
|
|
|
|
|
default n
|
|
|
|
|
help
|
2008-02-07 08:28:02 +08:00
|
|
|
This option supports a custom DSDT by optionally loading it from initrd.
|
|
|
|
|
See Documentation/acpi/dsdt-override.txt
|
|
|
|
|
|
|
|
|
|
If you are not using this feature now, but may use it later,
|
|
|
|
|
it is safe to say Y here.
|
2008-02-05 07:04:06 +08:00
|
|
|
|
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
|
|
|
|
|
enter a 4-digit year, eg. 2001 to disable ACPI by default
|
|
|
|
|
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
|
|
|
|
|
The ACPI driver can optionally report errors with a great deal
|
|
|
|
|
of verbosity. Saying Y enables these statements. This will increase
|
|
|
|
|
your kernel size by around 50K.
|
|
|
|
|
|
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.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config ACPI_EC
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This driver is required on some systems for the proper operation of
|
|
|
|
|
the battery and thermal drivers. If you are compiling for a
|
|
|
|
|
mobile system, say Y.
|
|
|
|
|
|
|
|
|
|
config ACPI_POWER
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config ACPI_SYSTEM
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This driver will enable your system to shut down using ACPI, and
|
|
|
|
|
dump your ACPI DSDT table using /proc/acpi/dsdt.
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
tristate "ACPI0004,PNP0A05 and PNP0A06 Container Driver (EXPERIMENTAL)"
|
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
default (ACPI_HOTPLUG_MEMORY || ACPI_HOTPLUG_CPU || ACPI_HOTPLUG_IO)
|
|
|
|
|
---help---
|
2005-03-02 13:00:00 +08:00
|
|
|
This allows _physical_ insertion and removal of CPUs and memory.
|
|
|
|
|
This can be useful, for example, on NUMA machines that support
|
|
|
|
|
ACPI based physical hotplug of nodes, or non-NUMA machines that
|
|
|
|
|
support physical cpu/memory hot-plug.
|
|
|
|
|
|
|
|
|
|
If one selects "m", this driver can be loaded with
|
|
|
|
|
"modprobe acpi_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
|
|
|
|
|
This driver adds supports for ACPI Memory Hotplug. This driver
|
|
|
|
|
provides support for fielding notifications on ACPI memory
|
|
|
|
|
devices (PNP0C80) which represent memory ranges that may be
|
|
|
|
|
onlined or offlined during runtime.
|
|
|
|
|
|
|
|
|
|
Enabling this driver assumes that your platform hardware
|
|
|
|
|
and firmware have support for hot-plugging physical memory. If
|
|
|
|
|
your system does not support physically adding or ripping out
|
2006-10-04 04:24:43 +08:00
|
|
|
memory DIMMs at some platform defined granularity (individually
|
2005-04-17 06:20:36 +08:00
|
|
|
or as a bank) at runtime, then you need not enable this driver.
|
|
|
|
|
|
|
|
|
|
If one selects "m," this driver can be loaded using the following
|
|
|
|
|
command:
|
|
|
|
|
$>modprobe 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
|
2007-09-26 23:43:48 +08:00
|
|
|
This driver adds support for the Smart Battery System, another
|
|
|
|
|
type of access to battery information, found on some laptops.
|
2006-07-01 23:36:54 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
endif # ACPI
|