aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/acpi/Kconfig
diff options
context:
space:
mode:
authorZhao Yakui <yakui.zhao@intel.com>2010-12-07 21:10:18 -0500
committerLen Brown <len.brown@intel.com>2010-12-14 00:22:14 -0500
commite92b297cc72ade7a58eaec7e01c906d856f8ab6e (patch)
tree098f92ee2ffed488e5c6438bc2e93c3212edbf25 /drivers/acpi/Kconfig
parent37bf501bdda1d5d6ea73ce29d4b00d291b6f3811 (diff)
IPMI/ACPI: Add the IPMI opregion driver to enable ACPI to access BMC controller
ACPI 4.0 spec adds the ACPI IPMI opregion, which means that the ACPI AML code can also communicate with the BMC controller. This is to install the ACPI IPMI opregion and enable the ACPI to access the BMC controller through the IPMI message. It will create IPMI user interface for every IPMI device detected in ACPI namespace and install the corresponding IPMI opregion space handler. Then it can enable ACPI to access the BMC controller through the IPMI message. The following describes how to process the IPMI request in IPMI space handler: 1. format the IPMI message based on the request in AML code. IPMI system address. Now the address type is SYSTEM_INTERFACE_ADDR_TYPE IPMI net function & command IPMI message payload 2. send the IPMI message by using the function of ipmi_request_settime 3. wait for the completion of IPMI message. It can be done in different routes: One is in handled in IPMI user recv callback function. Another is handled in timeout function. 4. format the IPMI response and return it to ACPI AML code. At the same time it also addes the module dependency. The ACPI IPMI opregion will depend on the IPMI subsystem. Signed-off-by: Zhao Yakui <yakui.zhao@intel.com> cc: Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by: Corey Minyard <cminyard@mvista.com> Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'drivers/acpi/Kconfig')
-rw-r--r--drivers/acpi/Kconfig11
1 files changed, 11 insertions, 0 deletions
diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
index 3f3489c5ca8c..a0c03658b2ea 100644
--- a/drivers/acpi/Kconfig
+++ b/drivers/acpi/Kconfig
@@ -209,6 +209,17 @@ config ACPI_PROCESSOR
209 209
210 To compile this driver as a module, choose M here: 210 To compile this driver as a module, choose M here:
211 the module will be called processor. 211 the module will be called processor.
212config ACPI_IPMI
213 tristate "IPMI"
214 depends on EXPERIMENTAL && IPMI_SI && IPMI_HANDLER
215 default n
216 help
217 This driver enables the ACPI to access the BMC controller. And it
218 uses the IPMI request/response message to communicate with BMC
219 controller, which can be found on on the server.
220
221 To compile this driver as a module, choose M here:
222 the module will be called as acpi_ipmi.
212 223
213config ACPI_HOTPLUG_CPU 224config ACPI_HOTPLUG_CPU
214 bool 225 bool