Kconfig 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # Intel network device configuration
  4. #
  5. config NET_VENDOR_INTEL
  6. bool "Intel devices"
  7. default y
  8. help
  9. If you have a network (Ethernet) card belonging to this class, say Y.
  10. Note that the answer to this question doesn't directly affect the
  11. kernel: saying N will just cause the configurator to skip all
  12. the questions about Intel cards. If you say Y, you will be asked for
  13. your specific card in the following questions.
  14. if NET_VENDOR_INTEL
  15. source "drivers/net/ethernet/intel/libeth/Kconfig"
  16. source "drivers/net/ethernet/intel/libie/Kconfig"
  17. config E100
  18. tristate "Intel(R) PRO/100+ support"
  19. depends on PCI
  20. select MII
  21. help
  22. This driver supports Intel(R) PRO/100 family of adapters.
  23. To verify that your adapter is supported, find the board ID number
  24. on the adapter. Look for a label that has a barcode and a number
  25. in the format 123456-001 (six digits hyphen three digits).
  26. Use the above information and the Adapter & Driver ID Guide that
  27. can be located at:
  28. <http://support.intel.com>
  29. to identify the adapter.
  30. More specific information on configuring the driver is in
  31. <file:Documentation/networking/device_drivers/ethernet/intel/e100.rst>.
  32. To compile this driver as a module, choose M here. The module
  33. will be called e100.
  34. config E1000
  35. tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
  36. depends on PCI && HAS_IOPORT
  37. help
  38. This driver supports Intel(R) PRO/1000 gigabit ethernet family of
  39. adapters. For more information on how to identify your adapter, go
  40. to the Adapter & Driver ID Guide that can be located at:
  41. <http://support.intel.com>
  42. More specific information on configuring the driver is in
  43. <file:Documentation/networking/device_drivers/ethernet/intel/e1000.rst>.
  44. To compile this driver as a module, choose M here. The module
  45. will be called e1000.
  46. config E1000E
  47. tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
  48. depends on PCI && (!SPARC32 || BROKEN)
  49. depends on PTP_1588_CLOCK_OPTIONAL
  50. select CRC32
  51. help
  52. This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
  53. ethernet family of adapters. For PCI or PCI-X e1000 adapters,
  54. use the regular e1000 driver For more information on how to
  55. identify your adapter, go to the Adapter & Driver ID Guide that
  56. can be located at:
  57. <http://support.intel.com>
  58. More specific information on configuring the driver is in
  59. <file:Documentation/networking/device_drivers/ethernet/intel/e1000e.rst>.
  60. To compile this driver as a module, choose M here. The module
  61. will be called e1000e.
  62. config E1000E_HWTS
  63. bool "Support HW cross-timestamp on PCH devices"
  64. default y
  65. depends on E1000E && X86
  66. help
  67. Say Y to enable hardware supported cross-timestamping on PCH
  68. devices. The cross-timestamp is available through the PTP clock
  69. driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE).
  70. config IGB
  71. tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
  72. depends on PCI
  73. depends on PTP_1588_CLOCK_OPTIONAL
  74. select I2C
  75. select I2C_ALGOBIT
  76. help
  77. This driver supports Intel(R) 82575/82576 gigabit ethernet family of
  78. adapters. For more information on how to identify your adapter, go
  79. to the Adapter & Driver ID Guide that can be located at:
  80. <http://support.intel.com>
  81. More specific information on configuring the driver is in
  82. <file:Documentation/networking/device_drivers/ethernet/intel/igb.rst>.
  83. To compile this driver as a module, choose M here. The module
  84. will be called igb.
  85. config IGB_HWMON
  86. bool "Intel(R) PCI-Express Gigabit adapters HWMON support"
  87. default y
  88. depends on IGB && HWMON && !(IGB=y && HWMON=m)
  89. help
  90. Say Y if you want to expose thermal sensor data on Intel devices.
  91. Some of our devices contain thermal sensors, both external and internal.
  92. This data is available via the hwmon sysfs interface and exposes
  93. the onboard sensors.
  94. config IGB_DCA
  95. bool "Direct Cache Access (DCA) Support"
  96. default y
  97. depends on IGB && DCA && !(IGB=y && DCA=m)
  98. help
  99. Say Y here if you want to use Direct Cache Access (DCA) in the
  100. driver. DCA is a method for warming the CPU cache before data
  101. is used, with the intent of lessening the impact of cache misses.
  102. config IGBVF
  103. tristate "Intel(R) 82576 Virtual Function Ethernet support"
  104. depends on PCI
  105. help
  106. This driver supports Intel(R) 82576 virtual functions. For more
  107. information on how to identify your adapter, go to the Adapter &
  108. Driver ID Guide that can be located at:
  109. <http://support.intel.com>
  110. More specific information on configuring the driver is in
  111. <file:Documentation/networking/device_drivers/ethernet/intel/igbvf.rst>.
  112. To compile this driver as a module, choose M here. The module
  113. will be called igbvf.
  114. config IXGBE
  115. tristate "Intel(R) 10GbE PCI Express adapters support"
  116. depends on PCI
  117. depends on PTP_1588_CLOCK_OPTIONAL
  118. select LIBIE_FWLOG if DEBUG_FS
  119. select MDIO
  120. select NET_DEVLINK
  121. select PLDMFW
  122. select PHYLIB
  123. help
  124. This driver supports Intel(R) 10GbE PCI Express family of
  125. adapters. For more information on how to identify your adapter, go
  126. to the Adapter & Driver ID Guide that can be located at:
  127. <http://support.intel.com>
  128. More specific information on configuring the driver is in
  129. <file:Documentation/networking/device_drivers/ethernet/intel/ixgbe.rst>.
  130. To compile this driver as a module, choose M here. The module
  131. will be called ixgbe.
  132. config IXGBE_HWMON
  133. bool "Intel(R) 10GbE PCI Express adapters HWMON support"
  134. default y
  135. depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m)
  136. help
  137. Say Y if you want to expose the thermal sensor data on some of
  138. our cards, via a hwmon sysfs interface.
  139. config IXGBE_DCA
  140. bool "Direct Cache Access (DCA) Support"
  141. default y
  142. depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
  143. help
  144. Say Y here if you want to use Direct Cache Access (DCA) in the
  145. driver. DCA is a method for warming the CPU cache before data
  146. is used, with the intent of lessening the impact of cache misses.
  147. config IXGBE_DCB
  148. bool "Data Center Bridging (DCB) Support"
  149. default n
  150. depends on IXGBE && DCB
  151. help
  152. Say Y here if you want to use Data Center Bridging (DCB) in the
  153. driver.
  154. If unsure, say N.
  155. config IXGBE_IPSEC
  156. bool "IPSec XFRM cryptography-offload acceleration"
  157. depends on IXGBE
  158. depends on XFRM_OFFLOAD
  159. default y
  160. select XFRM_ALGO
  161. help
  162. Enable support for IPSec offload in ixgbe.ko
  163. config IXGBEVF
  164. tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support"
  165. depends on PCI_MSI
  166. help
  167. This driver supports Intel(R) PCI Express virtual functions for the
  168. Intel(R) ixgbe driver. For more information on how to identify your
  169. adapter, go to the Adapter & Driver ID Guide that can be located at:
  170. <http://support.intel.com>
  171. More specific information on configuring the driver is in
  172. <file:Documentation/networking/device_drivers/ethernet/intel/ixgbevf.rst>.
  173. To compile this driver as a module, choose M here. The module
  174. will be called ixgbevf. MSI-X interrupt support is required
  175. for this driver to work correctly.
  176. config IXGBEVF_IPSEC
  177. bool "IPSec XFRM cryptography-offload acceleration"
  178. depends on IXGBEVF
  179. depends on XFRM_OFFLOAD
  180. default y
  181. select XFRM_ALGO
  182. help
  183. Enable support for IPSec offload in ixgbevf.ko
  184. config I40E
  185. tristate "Intel(R) Ethernet Controller XL710 Family support"
  186. depends on PTP_1588_CLOCK_OPTIONAL
  187. depends on PCI
  188. select AUXILIARY_BUS
  189. select LIBIE
  190. select LIBIE_ADMINQ
  191. select NET_DEVLINK
  192. help
  193. This driver supports Intel(R) Ethernet Controller XL710 Family of
  194. devices. For more information on how to identify your adapter, go
  195. to the Adapter & Driver ID Guide that can be located at:
  196. <http://support.intel.com>
  197. More specific information on configuring the driver is in
  198. <file:Documentation/networking/device_drivers/ethernet/intel/i40e.rst>.
  199. To compile this driver as a module, choose M here. The module
  200. will be called i40e.
  201. config I40E_DCB
  202. bool "Data Center Bridging (DCB) Support"
  203. default n
  204. depends on I40E && DCB
  205. help
  206. Say Y here if you want to use Data Center Bridging (DCB) in the
  207. driver.
  208. If unsure, say N.
  209. # this is here to allow seamless migration from I40EVF --> IAVF name
  210. # so that CONFIG_IAVF symbol will always mirror the state of CONFIG_I40EVF
  211. config IAVF
  212. tristate
  213. select LIBIE
  214. select LIBIE_ADMINQ
  215. select NET_SHAPER
  216. config I40EVF
  217. tristate "Intel(R) Ethernet Adaptive Virtual Function support"
  218. select IAVF
  219. depends on PCI_MSI
  220. depends on PTP_1588_CLOCK_OPTIONAL
  221. help
  222. This driver supports virtual functions for Intel XL710,
  223. X710, X722, XXV710, and all devices advertising support for
  224. Intel Ethernet Adaptive Virtual Function devices. For more
  225. information on how to identify your adapter, go to the Adapter
  226. & Driver ID Guide that can be located at:
  227. <https://support.intel.com>
  228. This driver was formerly named i40evf.
  229. More specific information on configuring the driver is in
  230. <file:Documentation/networking/device_drivers/ethernet/intel/iavf.rst>.
  231. To compile this driver as a module, choose M here. The module
  232. will be called iavf. MSI-X interrupt support is required
  233. for this driver to work correctly.
  234. config ICE
  235. tristate "Intel(R) Ethernet Connection E800 Series Support"
  236. default n
  237. depends on PCI_MSI
  238. depends on PTP_1588_CLOCK_OPTIONAL
  239. depends on GNSS || GNSS = n
  240. select AUXILIARY_BUS
  241. select DIMLIB
  242. select LIBETH_XDP
  243. select LIBIE
  244. select LIBIE_ADMINQ
  245. select LIBIE_FWLOG if DEBUG_FS
  246. select NET_DEVLINK
  247. select PACKING
  248. select PLDMFW
  249. select DPLL
  250. help
  251. This driver supports Intel(R) Ethernet Connection E800 Series of
  252. devices. For more information on how to identify your adapter, go
  253. to the Adapter & Driver ID Guide that can be located at:
  254. <http://support.intel.com>
  255. More specific information on configuring the driver is in
  256. <file:Documentation/networking/device_drivers/ethernet/intel/ice.rst>.
  257. To compile this driver as a module, choose M here. The module
  258. will be called ice.
  259. config ICE_HWMON
  260. bool "Intel(R) Ethernet Connection E800 Series Support HWMON support"
  261. default y
  262. depends on ICE && HWMON && !(ICE=y && HWMON=m)
  263. help
  264. Say Y if you want to expose thermal sensor data on Intel devices.
  265. Some of our devices contain internal thermal sensors.
  266. This data is available via the hwmon sysfs interface and exposes
  267. the onboard sensors.
  268. config ICE_SWITCHDEV
  269. bool "Switchdev Support"
  270. default y
  271. depends on ICE && NET_SWITCHDEV
  272. help
  273. Switchdev support provides internal SRIOV packet steering and switching.
  274. To enable it on running kernel use devlink tool:
  275. #devlink dev eswitch set pci/0000:XX:XX.X mode switchdev
  276. Say Y here if you want to use Switchdev in the driver.
  277. If unsure, say N.
  278. config ICE_HWTS
  279. bool "Support HW cross-timestamp on platforms with PTM support"
  280. default y
  281. depends on ICE && X86 && PCIE_PTM
  282. help
  283. Say Y to enable hardware supported cross-timestamping on platforms
  284. with PCIe PTM support. The cross-timestamp is available through
  285. the PTP clock driver precise cross-timestamp ioctl
  286. (PTP_SYS_OFFSET_PRECISE).
  287. config FM10K
  288. tristate "Intel(R) FM10000 Ethernet Switch Host Interface Support"
  289. default n
  290. depends on PCI_MSI
  291. depends on PTP_1588_CLOCK_OPTIONAL
  292. help
  293. This driver supports Intel(R) FM10000 Ethernet Switch Host
  294. Interface. For more information on how to identify your adapter,
  295. go to the Adapter & Driver ID Guide that can be located at:
  296. <http://support.intel.com>
  297. More specific information on configuring the driver is in
  298. <file:Documentation/networking/device_drivers/ethernet/intel/fm10k.rst>.
  299. To compile this driver as a module, choose M here. The module
  300. will be called fm10k. MSI-X interrupt support is required
  301. config IGC
  302. tristate "Intel(R) Ethernet Controller I225-LM/I225-V support"
  303. default n
  304. depends on PCI
  305. depends on PTP_1588_CLOCK_OPTIONAL
  306. depends on ETHTOOL_NETLINK
  307. help
  308. This driver supports Intel(R) Ethernet Controller I225-LM/I225-V
  309. family of adapters.
  310. For more information on how to identify your adapter, go
  311. to the Adapter & Driver ID Guide that can be located at:
  312. <http://support.intel.com>
  313. To compile this driver as a module, choose M here. The module
  314. will be called igc.
  315. config IGC_LEDS
  316. def_bool LEDS_TRIGGER_NETDEV
  317. depends on IGC && LEDS_CLASS
  318. depends on LEDS_CLASS=y || IGC=m
  319. help
  320. Optional support for controlling the NIC LED's with the netdev
  321. LED trigger.
  322. source "drivers/net/ethernet/intel/idpf/Kconfig"
  323. endif # NET_VENDOR_INTEL