add stmac read mac form eeprom

hc

2023-12-09 b22da3d8526a935aa31e086e63f60ff3246cb61c

 kernel/drivers/staging/greybus/Kconfig
..
..
@@ -1,45 +1,31 @@
1
-menuconfig GREYBUS
2
-	tristate "Greybus support"
3
-	depends on SYSFS
4
-	---help---
5
-	  This option enables the Greybus driver core.  Greybus is an
6
-	  hardware protocol that was designed to provide Unipro with a
7
-	  sane application layer.  It was originally designed for the
8
-	  ARA project, a module phone system, but has shown up in other
9
-	  phones, and can be tunneled over other busses in order to
10
-	  control hardware devices.
11
-
12
-	  Say Y here to enable support for these types of drivers.
13
-
14
-	  To compile this code as a module, chose M here: the module
15
-	  will be called greybus.ko
16
-
1
+# SPDX-License-Identifier: GPL-2.0
17
2
 if GREYBUS
18
-
19
-config GREYBUS_ES2
20
-	tristate "Greybus ES3 USB host controller"
21
-	depends on USB
22
-	---help---
23
-	  Select this option if you have a Toshiba ES3 USB device that
24
-	  acts as a Greybus "host controller".  This device is a bridge
25
-	  from a USB device to a Unipro network.
26
-
27
-	  To compile this code as a module, chose M here: the module
28
-	  will be called gb-es2.ko
29
3
 
30
4
 config GREYBUS_AUDIO
31
5
 	tristate "Greybus Audio Class driver"
32
-	depends on SOUND
33
-	---help---
6
+	depends on SOUND && SND_SOC
7
+	help
34
8
 	  Select this option if you have a device that follows the
35
9
 	  Greybus Audio Class specification.
36
10
 
37
11
 	  To compile this code as a module, chose M here: the module
38
12
 	  will be called gb-audio.ko
39
13
 
14
+config GREYBUS_AUDIO_APB_CODEC
15
+	tristate "Greybus APBridge Audio codec driver"
16
+	depends on SND_SOC && GREYBUS_AUDIO
17
+	help
18
+	  Select this option if you have a Toshiba APB device that has I2S
19
+          ports and acts as a Greybus "Dummy codec". This device is a
20
+          bridge from an APB-I2S port to a Unipro network.
21
+
22
+	  To compile this code as a module, chose M here: the module
23
+	  will be called gb-audio-codec.ko
24
+
25
+
40
26
 config GREYBUS_BOOTROM
41
27
 	tristate "Greybus Bootrom Class driver"
42
-	---help---
28
+	help
43
29
 	  Select this option if you have a device that follows the
44
30
 	  Greybus Bootrom Class specification.
45
31
 
..
..
@@ -49,7 +35,7 @@
49
35
 config GREYBUS_CAMERA
50
36
 	tristate "Greybus Camera Class driver"
51
37
 	depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN
52
-	---help---
38
+	help
53
39
 	  Select this option if you have a device that follows the
54
40
 	  Greybus Camera Class specification.
55
41
 
..
..
@@ -59,7 +45,7 @@
59
45
 config GREYBUS_FIRMWARE
60
46
 	tristate "Greybus Firmware Download Class driver"
61
47
 	depends on SPI
62
-	---help---
48
+	help
63
49
 	  Select this option if you have a device that follows the
64
50
 	  Greybus Firmware Download Class specification.
65
51
 
..
..
@@ -69,7 +55,7 @@
69
55
 config GREYBUS_HID
70
56
 	tristate "Greybus HID Class driver"
71
57
 	depends on HID && INPUT
72
-	---help---
58
+	help
73
59
 	  Select this option if you have a device that follows the
74
60
 	  Greybus HID Class specification.
75
61
 
..
..
@@ -79,7 +65,7 @@
79
65
 config GREYBUS_LIGHT
80
66
 	tristate "Greybus LED Class driver"
81
67
 	depends on LEDS_CLASS
82
-	---help---
68
+	help
83
69
 	  Select this option if you have a device that follows the
84
70
 	  Greybus LED Class specification.
85
71
 
..
..
@@ -88,7 +74,7 @@
88
74
 
89
75
 config GREYBUS_LOG
90
76
 	tristate "Greybus Debug Log Class driver"
91
-	---help---
77
+	help
92
78
 	  Select this option if you have a device that follows the
93
79
 	  Greybus Debug Log Class specification.
94
80
 
..
..
@@ -97,7 +83,7 @@
97
83
 
98
84
 config GREYBUS_LOOPBACK
99
85
 	tristate "Greybus Loopback Class driver"
100
-	---help---
86
+	help
101
87
 	  Select this option if you have a device that follows the
102
88
 	  Greybus Debug Log Class specification.
103
89
 
..
..
@@ -107,7 +93,7 @@
107
93
 config GREYBUS_POWER
108
94
 	tristate "Greybus Powersupply Class driver"
109
95
 	depends on POWER_SUPPLY
110
-	---help---
96
+	help
111
97
 	  Select this option if you have a device that follows the
112
98
 	  Greybus Powersupply Class specification.
113
99
 
..
..
@@ -116,7 +102,7 @@
116
102
 
117
103
 config GREYBUS_RAW
118
104
 	tristate "Greybus Raw Class driver"
119
-	---help---
105
+	help
120
106
 	  Select this option if you have a device that follows the
121
107
 	  Greybus Raw Class specification.
122
108
 
..
..
@@ -125,7 +111,7 @@
125
111
 
126
112
 config GREYBUS_VIBRATOR
127
113
 	tristate "Greybus Vibrator Motor Class driver"
128
-	---help---
114
+	help
129
115
 	  Select this option if you have a device that follows the
130
116
 	  Greybus Vibrator Motor Class specification.
131
117
 
..
..
@@ -134,7 +120,7 @@
134
120
 
135
121
 menuconfig GREYBUS_BRIDGED_PHY
136
122
 	tristate "Greybus Bridged PHY Class drivers"
137
-	---help---
123
+	help
138
124
 	  Select this option to pick from a variety of Greybus Bridged
139
125
 	  PHY class drivers.  These drivers emulate a number of
140
126
 	  different "traditional" busses by tunneling them over Greybus.
..
..
@@ -148,7 +134,8 @@
148
134
 config GREYBUS_GPIO
149
135
 	tristate "Greybus GPIO Bridged PHY driver"
150
136
 	depends on GPIOLIB
151
-	---help---
137
+	select GPIOLIB_IRQCHIP
138
+	help
152
139
 	  Select this option if you have a device that follows the
153
140
 	  Greybus GPIO Bridged PHY Class specification.
154
141
 
..
..
@@ -158,7 +145,7 @@
158
145
 config GREYBUS_I2C
159
146
 	tristate "Greybus I2C Bridged PHY driver"
160
147
 	depends on I2C
161
-	---help---
148
+	help
162
149
 	  Select this option if you have a device that follows the
163
150
 	  Greybus I2C Bridged PHY Class specification.
164
151
 
..
..
@@ -168,7 +155,7 @@
168
155
 config GREYBUS_PWM
169
156
 	tristate "Greybus PWM Bridged PHY driver"
170
157
 	depends on PWM
171
-	---help---
158
+	help
172
159
 	  Select this option if you have a device that follows the
173
160
 	  Greybus PWM Bridged PHY Class specification.
174
161
 
..
..
@@ -178,7 +165,7 @@
178
165
 config GREYBUS_SDIO
179
166
 	tristate "Greybus SDIO Bridged PHY driver"
180
167
 	depends on MMC
181
-	---help---
168
+	help
182
169
 	  Select this option if you have a device that follows the
183
170
 	  Greybus SDIO Bridged PHY Class specification.
184
171
 
..
..
@@ -188,7 +175,7 @@
188
175
 config GREYBUS_SPI
189
176
 	tristate "Greybus SPI Bridged PHY driver"
190
177
 	depends on SPI
191
-	---help---
178
+	help
192
179
 	  Select this option if you have a device that follows the
193
180
 	  Greybus SPI Bridged PHY Class specification.
194
181
 
..
..
@@ -198,7 +185,7 @@
198
185
 config GREYBUS_UART
199
186
 	tristate "Greybus UART Bridged PHY driver"
200
187
 	depends on TTY
201
-	---help---
188
+	help
202
189
 	  Select this option if you have a device that follows the
203
190
 	  Greybus UART Bridged PHY Class specification.
204
191
 
..
..
@@ -208,7 +195,7 @@
208
195
 config GREYBUS_USB
209
196
 	tristate "Greybus USB Host Bridged PHY driver"
210
197
 	depends on USB
211
-	---help---
198
+	help
212
199
 	  Select this option if you have a device that follows the
213
200
 	  Greybus USB Host Bridged PHY Class specification.
214
201
 
..
..
@@ -220,7 +207,7 @@
220
207
 config GREYBUS_ARCHE
221
208
 	tristate "Greybus Arche Platform driver"
222
209
 	depends on USB_HSIC_USB3613 || COMPILE_TEST
223
-	---help---
210
+	help
224
211
 	  Select this option if you have an Arche device.
225
212
 
226
213
 	  To compile this code as a module, chose M here: the module