add gpio led uart

hc

2024-05-10 748e4f3d702def1a4bff191e0cf93b6a05340f01

 kernel/drivers/char/ipmi/Kconfig
..
..
@@ -1,36 +1,41 @@
1
+# SPDX-License-Identifier: GPL-2.0-only
1
2
 #
2
3
 # IPMI device configuration
3
4
 #
4
5
 
5
6
 menuconfig IPMI_HANDLER
6
-       tristate 'IPMI top-level message handler'
7
-       depends on HAS_IOMEM
8
-       select IPMI_DMI_DECODE if DMI
9
-       help
10
-         This enables the central IPMI message handler, required for IPMI
11
-	 to work.
7
+	tristate 'IPMI top-level message handler'
8
+	depends on HAS_IOMEM
9
+	select IPMI_DMI_DECODE if DMI
10
+	help
11
+	  This enables the central IPMI message handler, required for IPMI
12
+	  to work.
12
13
 
13
-         IPMI is a standard for managing sensors (temperature,
14
-         voltage, etc.) in a system.
14
+	  IPMI is a standard for managing sensors (temperature,
15
+	  voltage, etc.) in a system.
15
16
 
16
-         See <file:Documentation/IPMI.txt> for more details on the driver.
17
+	  See <file:Documentation/driver-api/ipmi.rst> for more details on the driver.
17
18
 
18
-	 If unsure, say N.
19
+	  If unsure, say N.
19
20
 
20
21
 config IPMI_DMI_DECODE
21
-       bool
22
+	select IPMI_PLAT_DATA
23
+	bool
24
+
25
+config IPMI_PLAT_DATA
26
+	bool
22
27
 
23
28
 if IPMI_HANDLER
24
29
 
25
30
 config IPMI_PANIC_EVENT
26
-       bool 'Generate a panic event to all BMCs on a panic'
27
-       help
28
-	 When a panic occurs, this will cause the IPMI message handler to,
29
-	 by default, generate an IPMI event describing the panic to each
30
-	 interface registered with the message handler.  This is always
31
-	 available, the module parameter for ipmi_msghandler named
32
-	 panic_op can be set to "event" to chose this value, this config
33
-	 simply causes the default value to be set to "event".
31
+	bool 'Generate a panic event to all BMCs on a panic'
32
+	help
33
+	  When a panic occurs, this will cause the IPMI message handler to,
34
+	  by default, generate an IPMI event describing the panic to each
35
+	  interface registered with the message handler.  This is always
36
+	  available, the module parameter for ipmi_msghandler named
37
+	  panic_op can be set to "event" to chose this value, this config
38
+	  simply causes the default value to be set to "event".
34
39
 
35
40
 config IPMI_PANIC_STRING
36
41
 	bool 'Generate OEM events containing the panic string'
..
..
@@ -49,42 +54,43 @@
49
54
 	  causes the default value to be set to "string".
50
55
 
51
56
 config IPMI_DEVICE_INTERFACE
52
-       tristate 'Device interface for IPMI'
53
-       help
54
-         This provides an IOCTL interface to the IPMI message handler so
55
-	 userland processes may use IPMI.  It supports poll() and select().
57
+	tristate 'Device interface for IPMI'
58
+	help
59
+	  This provides an IOCTL interface to the IPMI message handler so
60
+	  userland processes may use IPMI.  It supports poll() and select().
56
61
 
57
62
 config IPMI_SI
58
-       tristate 'IPMI System Interface handler'
59
-       help
60
-         Provides a driver for System Interfaces (KCS, SMIC, BT).
61
-	 Currently, only KCS and SMIC are supported.  If
62
-	 you are using IPMI, you should probably say "y" here.
63
+	tristate 'IPMI System Interface handler'
64
+	select IPMI_PLAT_DATA
65
+	help
66
+	  Provides a driver for System Interfaces (KCS, SMIC, BT).
67
+	  Currently, only KCS and SMIC are supported.  If
68
+	  you are using IPMI, you should probably say "y" here.
63
69
 
64
70
 config IPMI_SSIF
65
-       tristate 'IPMI SMBus handler (SSIF)'
66
-       select I2C
67
-       help
68
-         Provides a driver for a SMBus interface to a BMC, meaning that you
69
-	 have a driver that must be accessed over an I2C bus instead of a
70
-	 standard interface.  This module requires I2C support.
71
+	tristate 'IPMI SMBus handler (SSIF)'
72
+	select I2C
73
+	help
74
+	  Provides a driver for a SMBus interface to a BMC, meaning that you
75
+	  have a driver that must be accessed over an I2C bus instead of a
76
+	  standard interface.  This module requires I2C support.
71
77
 
72
78
 config IPMI_POWERNV
73
-       depends on PPC_POWERNV
74
-       tristate 'POWERNV (OPAL firmware) IPMI interface'
75
-       help
76
-         Provides a driver for OPAL firmware-based IPMI interfaces.
79
+	depends on PPC_POWERNV
80
+	tristate 'POWERNV (OPAL firmware) IPMI interface'
81
+	help
82
+	  Provides a driver for OPAL firmware-based IPMI interfaces.
77
83
 
78
84
 config IPMI_WATCHDOG
79
-       tristate 'IPMI Watchdog Timer'
80
-       help
81
-         This enables the IPMI watchdog timer.
85
+	tristate 'IPMI Watchdog Timer'
86
+	help
87
+	  This enables the IPMI watchdog timer.
82
88
 
83
89
 config IPMI_POWEROFF
84
-       tristate 'IPMI Poweroff'
85
-       help
86
-         This enables a function to power off the system with IPMI if
87
-	 the IPMI management controller is capable of this.
90
+	tristate 'IPMI Poweroff'
91
+	help
92
+	  This enables a function to power off the system with IPMI if
93
+	  the IPMI management controller is capable of this.
88
94
 
89
95
 endif # IPMI_HANDLER
90
96
 
..
..
@@ -120,9 +126,19 @@
120
126
 
121
127
 config ASPEED_BT_IPMI_BMC
122
128
 	depends on ARCH_ASPEED || COMPILE_TEST
123
-       depends on REGMAP && REGMAP_MMIO && MFD_SYSCON
129
+	depends on MFD_SYSCON
130
+	select REGMAP_MMIO
124
131
 	tristate "BT IPMI bmc driver"
125
132
 	help
126
133
 	  Provides a driver for the BT (Block Transfer) IPMI interface
127
134
 	  found on Aspeed SOCs (AST2400 and AST2500). The driver
128
135
 	  implements the BMC side of the BT interface.
136
+
137
+config IPMB_DEVICE_INTERFACE
138
+	tristate 'IPMB Interface handler'
139
+	depends on I2C
140
+	depends on I2C_SLAVE
141
+	help
142
+	  Provides a driver for a device (Satellite MC) to
143
+	  receive requests and send responses back to the BMC via
144
+	  the IPMB interface. This module requires I2C support.