Kconfig 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990
  1. #
  2. # IPMI device configuration
  3. #
  4. menuconfig IPMI_HANDLER
  5. tristate 'IPMI top-level message handler'
  6. depends on HAS_IOMEM
  7. help
  8. This enables the central IPMI message handler, required for IPMI
  9. to work.
  10. IPMI is a standard for managing sensors (temperature,
  11. voltage, etc.) in a system.
  12. See <file:Documentation/IPMI.txt> for more details on the driver.
  13. If unsure, say N.
  14. if IPMI_HANDLER
  15. config IPMI_PANIC_EVENT
  16. bool 'Generate a panic event to all BMCs on a panic'
  17. help
  18. When a panic occurs, this will cause the IPMI message handler to
  19. generate an IPMI event describing the panic to each interface
  20. registered with the message handler.
  21. config IPMI_PANIC_STRING
  22. bool 'Generate OEM events containing the panic string'
  23. depends on IPMI_PANIC_EVENT
  24. help
  25. When a panic occurs, this will cause the IPMI message handler to
  26. generate IPMI OEM type f0 events holding the IPMB address of the
  27. panic generator (byte 4 of the event), a sequence number for the
  28. string (byte 5 of the event) and part of the string (the rest of the
  29. event). Bytes 1, 2, and 3 are the normal usage for an OEM event.
  30. You can fetch these events and use the sequence numbers to piece the
  31. string together.
  32. config IPMI_DEVICE_INTERFACE
  33. tristate 'Device interface for IPMI'
  34. help
  35. This provides an IOCTL interface to the IPMI message handler so
  36. userland processes may use IPMI. It supports poll() and select().
  37. config IPMI_SI
  38. tristate 'IPMI System Interface handler'
  39. help
  40. Provides a driver for System Interfaces (KCS, SMIC, BT).
  41. Currently, only KCS and SMIC are supported. If
  42. you are using IPMI, you should probably say "y" here.
  43. config IPMI_SI_PROBE_DEFAULTS
  44. bool 'Probe for all possible IPMI system interfaces by default'
  45. default n
  46. depends on IPMI_SI
  47. help
  48. Modern systems will usually expose IPMI interfaces via a discoverable
  49. firmware mechanism such as ACPI or DMI. Older systems do not, and so
  50. the driver is forced to probe hardware manually. This may cause boot
  51. delays. Say "n" here to disable this manual probing. IPMI will then
  52. only be available on older systems if the "ipmi_si_intf.trydefaults=1"
  53. boot argument is passed.
  54. config IPMI_SSIF
  55. tristate 'IPMI SMBus handler (SSIF)'
  56. select I2C
  57. help
  58. Provides a driver for a SMBus interface to a BMC, meaning that you
  59. have a driver that must be accessed over an I2C bus instead of a
  60. standard interface. This module requires I2C support.
  61. config IPMI_POWERNV
  62. depends on PPC_POWERNV
  63. tristate 'POWERNV (OPAL firmware) IPMI interface'
  64. help
  65. Provides a driver for OPAL firmware-based IPMI interfaces.
  66. config IPMI_WATCHDOG
  67. tristate 'IPMI Watchdog Timer'
  68. help
  69. This enables the IPMI watchdog timer.
  70. config IPMI_POWEROFF
  71. tristate 'IPMI Poweroff'
  72. help
  73. This enables a function to power off the system with IPMI if
  74. the IPMI management controller is capable of this.
  75. endif # IPMI_HANDLER