Loading...
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 | # # IPMI device configuration # menuconfig IPMI_HANDLER tristate 'IPMI top-level message handler' depends on HAS_IOMEM select IPMI_DMI_DECODE if DMI help This enables the central IPMI message handler, required for IPMI to work. IPMI is a standard for managing sensors (temperature, voltage, etc.) in a system. See <file:Documentation/IPMI.txt> for more details on the driver. If unsure, say N. config IPMI_DMI_DECODE bool if IPMI_HANDLER config IPMI_PROC_INTERFACE bool 'Provide an interface for IPMI stats in /proc (deprecated)' depends on PROC_FS default y help Do not use this any more, use sysfs for this info. It will be removed in future kernel versions. config IPMI_PANIC_EVENT bool 'Generate a panic event to all BMCs on a panic' help When a panic occurs, this will cause the IPMI message handler to, by default, generate an IPMI event describing the panic to each interface registered with the message handler. This is always available, the module parameter for ipmi_msghandler named panic_op can be set to "event" to chose this value, this config simply causes the default value to be set to "event". config IPMI_PANIC_STRING bool 'Generate OEM events containing the panic string' depends on IPMI_PANIC_EVENT help When a panic occurs, this will cause the IPMI message handler to, by default, generate IPMI OEM type f0 events holding the IPMB address of the panic generator (byte 4 of the event), a sequence number for the string (byte 5 of the event) and part of the string (the rest of the event). Bytes 1, 2, and 3 are the normal usage for an OEM event. You can fetch these events and use the sequence numbers to piece the string together. This config parameter sets the default value to generate these events, the module parameter for ipmi_msghandler named panic_op can be set to "string" to chose this value, this config simply causes the default value to be set to "string". config IPMI_DEVICE_INTERFACE tristate 'Device interface for IPMI' help This provides an IOCTL interface to the IPMI message handler so userland processes may use IPMI. It supports poll() and select(). config IPMI_SI tristate 'IPMI System Interface handler' help Provides a driver for System Interfaces (KCS, SMIC, BT). Currently, only KCS and SMIC are supported. If you are using IPMI, you should probably say "y" here. config IPMI_SSIF tristate 'IPMI SMBus handler (SSIF)' select I2C help Provides a driver for a SMBus interface to a BMC, meaning that you have a driver that must be accessed over an I2C bus instead of a standard interface. This module requires I2C support. config IPMI_POWERNV depends on PPC_POWERNV tristate 'POWERNV (OPAL firmware) IPMI interface' help Provides a driver for OPAL firmware-based IPMI interfaces. config IPMI_WATCHDOG tristate 'IPMI Watchdog Timer' help This enables the IPMI watchdog timer. config IPMI_POWEROFF tristate 'IPMI Poweroff' help This enables a function to power off the system with IPMI if the IPMI management controller is capable of this. endif # IPMI_HANDLER config ASPEED_BT_IPMI_BMC depends on ARCH_ASPEED || COMPILE_TEST depends on REGMAP && REGMAP_MMIO && MFD_SYSCON tristate "BT IPMI bmc driver" help Provides a driver for the BT (Block Transfer) IPMI interface found on Aspeed SOCs (AST2400 and AST2500). The driver implements the BMC side of the BT interface. |