blob: f6fa056a52fcfac0f846e5c6d2efb0df26452502 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# IPMI device configuration
3#
4
Jan Engelhardtbcf6b4b2007-07-15 23:39:28 -07005menuconfig IPMI_HANDLER
Linus Torvalds1da177e2005-04-16 15:20:36 -07006 tristate 'IPMI top-level message handler'
Jan Engelhardtbcf6b4b2007-07-15 23:39:28 -07007 depends on HAS_IOMEM
Corey Minyard9f881452017-06-09 21:19:52 -05008 select IPMI_DMI_DECODE if DMI
Linus Torvalds1da177e2005-04-16 15:20:36 -07009 help
10 This enables the central IPMI message handler, required for IPMI
11 to work.
12
13 IPMI is a standard for managing sensors (temperature,
14 voltage, etc.) in a system.
15
16 See <file:Documentation/IPMI.txt> for more details on the driver.
17
18 If unsure, say N.
19
Corey Minyard9f881452017-06-09 21:19:52 -050020config IPMI_DMI_DECODE
21 bool
22
Jan Engelhardtbcf6b4b2007-07-15 23:39:28 -070023if IPMI_HANDLER
24
Linus Torvalds1da177e2005-04-16 15:20:36 -070025config IPMI_PANIC_EVENT
26 bool 'Generate a panic event to all BMCs on a panic'
Linus Torvalds1da177e2005-04-16 15:20:36 -070027 help
28 When a panic occurs, this will cause the IPMI message handler to
29 generate an IPMI event describing the panic to each interface
30 registered with the message handler.
31
32config IPMI_PANIC_STRING
33 bool 'Generate OEM events containing the panic string'
34 depends on IPMI_PANIC_EVENT
35 help
36 When a panic occurs, this will cause the IPMI message handler to
37 generate IPMI OEM type f0 events holding the IPMB address of the
38 panic generator (byte 4 of the event), a sequence number for the
39 string (byte 5 of the event) and part of the string (the rest of the
40 event). Bytes 1, 2, and 3 are the normal usage for an OEM event.
41 You can fetch these events and use the sequence numbers to piece the
42 string together.
43
44config IPMI_DEVICE_INTERFACE
45 tristate 'Device interface for IPMI'
Linus Torvalds1da177e2005-04-16 15:20:36 -070046 help
47 This provides an IOCTL interface to the IPMI message handler so
48 userland processes may use IPMI. It supports poll() and select().
49
50config IPMI_SI
51 tristate 'IPMI System Interface handler'
Linus Torvalds1da177e2005-04-16 15:20:36 -070052 help
53 Provides a driver for System Interfaces (KCS, SMIC, BT).
54 Currently, only KCS and SMIC are supported. If
55 you are using IPMI, you should probably say "y" here.
56
Corey Minyard25930702012-03-19 16:00:55 -050057config IPMI_SSIF
58 tristate 'IPMI SMBus handler (SSIF)'
59 select I2C
60 help
61 Provides a driver for a SMBus interface to a BMC, meaning that you
62 have a driver that must be accessed over an I2C bus instead of a
63 standard interface. This module requires I2C support.
64
Jeremy Kerr6a11e5c2014-11-12 15:41:05 +080065config IPMI_POWERNV
66 depends on PPC_POWERNV
67 tristate 'POWERNV (OPAL firmware) IPMI interface'
68 help
69 Provides a driver for OPAL firmware-based IPMI interfaces.
70
Linus Torvalds1da177e2005-04-16 15:20:36 -070071config IPMI_WATCHDOG
72 tristate 'IPMI Watchdog Timer'
Linus Torvalds1da177e2005-04-16 15:20:36 -070073 help
74 This enables the IPMI watchdog timer.
75
76config IPMI_POWEROFF
77 tristate 'IPMI Poweroff'
Linus Torvalds1da177e2005-04-16 15:20:36 -070078 help
79 This enables a function to power off the system with IPMI if
80 the IPMI management controller is capable of this.
81
Jan Engelhardtbcf6b4b2007-07-15 23:39:28 -070082endif # IPMI_HANDLER
Alistair Popple54f9c4d2016-09-20 09:01:38 +020083
84config ASPEED_BT_IPMI_BMC
Andrew Jefferyeb994592017-02-21 01:53:00 +103085 depends on ARCH_ASPEED || COMPILE_TEST
86 depends on REGMAP && REGMAP_MMIO && MFD_SYSCON
Alistair Popple54f9c4d2016-09-20 09:01:38 +020087 tristate "BT IPMI bmc driver"
88 help
89 Provides a driver for the BT (Block Transfer) IPMI interface
90 found on Aspeed SOCs (AST2400 and AST2500). The driver
91 implements the BMC side of the BT interface.