e5f3155267
The 'imply' keyword does not do what most people think it does, it only
politely asks Kconfig to turn on another symbol, but does not prevent
it from being disabled manually or built as a loadable module when the
user is built-in. In the ICE driver, the latter now causes a link failure:
aarch64-linux-ld: drivers/net/ethernet/intel/ice/ice_main.o: in function `ice_eth_ioctl':
ice_main.c:(.text+0x13b0): undefined reference to `ice_ptp_get_ts_config'
ice_main.c:(.text+0x13b0): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `ice_ptp_get_ts_config'
aarch64-linux-ld: ice_main.c:(.text+0x13bc): undefined reference to `ice_ptp_set_ts_config'
ice_main.c:(.text+0x13bc): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `ice_ptp_set_ts_config'
aarch64-linux-ld: drivers/net/ethernet/intel/ice/ice_main.o: in function `ice_prepare_for_reset':
ice_main.c:(.text+0x31fc): undefined reference to `ice_ptp_release'
ice_main.c:(.text+0x31fc): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `ice_ptp_release'
aarch64-linux-ld: drivers/net/ethernet/intel/ice/ice_main.o: in function `ice_rebuild':
This is a recurring problem in many drivers, and we have discussed
it several times befores, without reaching a consensus. I'm providing
a link to the previous email thread for reference, which discusses
some related problems.
To solve the dependency issue better than the 'imply' keyword, introduce a
separate Kconfig symbol "CONFIG_PTP_1588_CLOCK_OPTIONAL" that any driver
can depend on if it is able to use PTP support when available, but works
fine without it. Whenever CONFIG_PTP_1588_CLOCK=m, those drivers are
then prevented from being built-in, the same way as with a 'depends on
PTP_1588_CLOCK || !PTP_1588_CLOCK' dependency that does the same trick,
but that can be rather confusing when you first see it.
Since this should cover the dependencies correctly, the IS_REACHABLE()
hack in the header is no longer needed now, and can be turned back
into a normal IS_ENABLED() check. Any driver that gets the dependency
wrong will now cause a link time failure rather than being unable to use
PTP support when that is in a loadable module.
However, the two recently added ptp_get_vclocks_index() and
ptp_convert_timestamp() interfaces are only called from builtin code with
ethtool and socket timestamps, so keep the current behavior by stubbing
those out completely when PTP is in a loadable module. This should be
addressed properly in a follow-up.
As Richard suggested, we may want to actually turn PTP support into a
'bool' option later on, preventing it from being a loadable module
altogether, which would be one way to solve the problem with the ethtool
interface.
Fixes: 06c16d89d2cb ("ice: register 1588 PTP clock device object for E810 devices")
Link: https://lore.kernel.org/netdev/20210804121318.337276-1-arnd@kernel.org/
Link: https://lore.kernel.org/netdev/CAK8P3a06enZOf=XyZ+zcAwBczv41UuCTz+=0FMf2gBz1_cOnZQ@mail.gmail.com/
Link: https://lore.kernel.org/netdev/CAK8P3a3=eOxE-K25754+fB_-i_0BZzf9a9RfPTX3ppSwu9WZXw@mail.gmail.com/
Link: https://lore.kernel.org/netdev/20210726084540.3282344-1-arnd@kernel.org/
Acked-by: Shannon Nelson <snelson@pensando.io>
Acked-by: Jacob Keller <jacob.e.keller@intel.com>
Acked-by: Richard Cochran <richardcochran@gmail.com>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Link: https://lore.kernel.org/r/20210812183509.1362782-1-arnd@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
351 lines
11 KiB
Plaintext
351 lines
11 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# Intel network device configuration
|
|
#
|
|
|
|
config NET_VENDOR_INTEL
|
|
bool "Intel devices"
|
|
default y
|
|
help
|
|
If you have a network (Ethernet) card belonging to this class, say Y.
|
|
|
|
Note that the answer to this question doesn't directly affect the
|
|
kernel: saying N will just cause the configurator to skip all
|
|
the questions about Intel cards. If you say Y, you will be asked for
|
|
your specific card in the following questions.
|
|
|
|
if NET_VENDOR_INTEL
|
|
|
|
config E100
|
|
tristate "Intel(R) PRO/100+ support"
|
|
depends on PCI
|
|
select MII
|
|
help
|
|
This driver supports Intel(R) PRO/100 family of adapters.
|
|
To verify that your adapter is supported, find the board ID number
|
|
on the adapter. Look for a label that has a barcode and a number
|
|
in the format 123456-001 (six digits hyphen three digits).
|
|
|
|
Use the above information and the Adapter & Driver ID Guide that
|
|
can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
to identify the adapter.
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/e100.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called e100.
|
|
|
|
config E1000
|
|
tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
|
|
depends on PCI
|
|
help
|
|
This driver supports Intel(R) PRO/1000 gigabit ethernet family of
|
|
adapters. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/e1000.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called e1000.
|
|
|
|
config E1000E
|
|
tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
|
|
depends on PCI && (!SPARC32 || BROKEN)
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
select CRC32
|
|
help
|
|
This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
|
|
ethernet family of adapters. For PCI or PCI-X e1000 adapters,
|
|
use the regular e1000 driver For more information on how to
|
|
identify your adapter, go to the Adapter & Driver ID Guide that
|
|
can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/e1000e.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called e1000e.
|
|
|
|
config E1000E_HWTS
|
|
bool "Support HW cross-timestamp on PCH devices"
|
|
default y
|
|
depends on E1000E && X86
|
|
help
|
|
Say Y to enable hardware supported cross-timestamping on PCH
|
|
devices. The cross-timestamp is available through the PTP clock
|
|
driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE).
|
|
|
|
config IGB
|
|
tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
|
|
depends on PCI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
select I2C
|
|
select I2C_ALGOBIT
|
|
help
|
|
This driver supports Intel(R) 82575/82576 gigabit ethernet family of
|
|
adapters. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/igb.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called igb.
|
|
|
|
config IGB_HWMON
|
|
bool "Intel(R) PCI-Express Gigabit adapters HWMON support"
|
|
default y
|
|
depends on IGB && HWMON && !(IGB=y && HWMON=m)
|
|
help
|
|
Say Y if you want to expose thermal sensor data on Intel devices.
|
|
|
|
Some of our devices contain thermal sensors, both external and internal.
|
|
This data is available via the hwmon sysfs interface and exposes
|
|
the onboard sensors.
|
|
|
|
config IGB_DCA
|
|
bool "Direct Cache Access (DCA) Support"
|
|
default y
|
|
depends on IGB && DCA && !(IGB=y && DCA=m)
|
|
help
|
|
Say Y here if you want to use Direct Cache Access (DCA) in the
|
|
driver. DCA is a method for warming the CPU cache before data
|
|
is used, with the intent of lessening the impact of cache misses.
|
|
|
|
config IGBVF
|
|
tristate "Intel(R) 82576 Virtual Function Ethernet support"
|
|
depends on PCI
|
|
help
|
|
This driver supports Intel(R) 82576 virtual functions. For more
|
|
information on how to identify your adapter, go to the Adapter &
|
|
Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/igbvf.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called igbvf.
|
|
|
|
config IXGB
|
|
tristate "Intel(R) PRO/10GbE support"
|
|
depends on PCI
|
|
help
|
|
This driver supports Intel(R) PRO/10GbE family of adapters for
|
|
PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
|
|
instead. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/ixgb.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called ixgb.
|
|
|
|
config IXGBE
|
|
tristate "Intel(R) 10GbE PCI Express adapters support"
|
|
depends on PCI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
select MDIO
|
|
select PHYLIB
|
|
help
|
|
This driver supports Intel(R) 10GbE PCI Express family of
|
|
adapters. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/ixgbe.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called ixgbe.
|
|
|
|
config IXGBE_HWMON
|
|
bool "Intel(R) 10GbE PCI Express adapters HWMON support"
|
|
default y
|
|
depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m)
|
|
help
|
|
Say Y if you want to expose the thermal sensor data on some of
|
|
our cards, via a hwmon sysfs interface.
|
|
|
|
config IXGBE_DCA
|
|
bool "Direct Cache Access (DCA) Support"
|
|
default y
|
|
depends on IXGBE && DCA && !(IXGBE=y && DCA=m)
|
|
help
|
|
Say Y here if you want to use Direct Cache Access (DCA) in the
|
|
driver. DCA is a method for warming the CPU cache before data
|
|
is used, with the intent of lessening the impact of cache misses.
|
|
|
|
config IXGBE_DCB
|
|
bool "Data Center Bridging (DCB) Support"
|
|
default n
|
|
depends on IXGBE && DCB
|
|
help
|
|
Say Y here if you want to use Data Center Bridging (DCB) in the
|
|
driver.
|
|
|
|
If unsure, say N.
|
|
|
|
config IXGBE_IPSEC
|
|
bool "IPSec XFRM cryptography-offload acceleration"
|
|
depends on IXGBE
|
|
depends on XFRM_OFFLOAD
|
|
default y
|
|
select XFRM_ALGO
|
|
help
|
|
Enable support for IPSec offload in ixgbe.ko
|
|
|
|
config IXGBEVF
|
|
tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support"
|
|
depends on PCI_MSI
|
|
help
|
|
This driver supports Intel(R) PCI Express virtual functions for the
|
|
Intel(R) ixgbe driver. For more information on how to identify your
|
|
adapter, go to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/ixgbevf.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called ixgbevf. MSI-X interrupt support is required
|
|
for this driver to work correctly.
|
|
|
|
config IXGBEVF_IPSEC
|
|
bool "IPSec XFRM cryptography-offload acceleration"
|
|
depends on IXGBEVF
|
|
depends on XFRM_OFFLOAD
|
|
default y
|
|
select XFRM_ALGO
|
|
help
|
|
Enable support for IPSec offload in ixgbevf.ko
|
|
|
|
config I40E
|
|
tristate "Intel(R) Ethernet Controller XL710 Family support"
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
depends on PCI
|
|
select AUXILIARY_BUS
|
|
help
|
|
This driver supports Intel(R) Ethernet Controller XL710 Family of
|
|
devices. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/i40e.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called i40e.
|
|
|
|
config I40E_DCB
|
|
bool "Data Center Bridging (DCB) Support"
|
|
default n
|
|
depends on I40E && DCB
|
|
help
|
|
Say Y here if you want to use Data Center Bridging (DCB) in the
|
|
driver.
|
|
|
|
If unsure, say N.
|
|
|
|
# this is here to allow seamless migration from I40EVF --> IAVF name
|
|
# so that CONFIG_IAVF symbol will always mirror the state of CONFIG_I40EVF
|
|
config IAVF
|
|
tristate
|
|
config I40EVF
|
|
tristate "Intel(R) Ethernet Adaptive Virtual Function support"
|
|
select IAVF
|
|
depends on PCI_MSI
|
|
help
|
|
This driver supports virtual functions for Intel XL710,
|
|
X710, X722, XXV710, and all devices advertising support for
|
|
Intel Ethernet Adaptive Virtual Function devices. For more
|
|
information on how to identify your adapter, go to the Adapter
|
|
& Driver ID Guide that can be located at:
|
|
|
|
<https://support.intel.com>
|
|
|
|
This driver was formerly named i40evf.
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/iavf.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called iavf. MSI-X interrupt support is required
|
|
for this driver to work correctly.
|
|
|
|
config ICE
|
|
tristate "Intel(R) Ethernet Connection E800 Series Support"
|
|
default n
|
|
depends on PCI_MSI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
select AUXILIARY_BUS
|
|
select DIMLIB
|
|
select NET_DEVLINK
|
|
select PLDMFW
|
|
help
|
|
This driver supports Intel(R) Ethernet Connection E800 Series of
|
|
devices. For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/ice.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called ice.
|
|
|
|
config FM10K
|
|
tristate "Intel(R) FM10000 Ethernet Switch Host Interface Support"
|
|
default n
|
|
depends on PCI_MSI
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
|
help
|
|
This driver supports Intel(R) FM10000 Ethernet Switch Host
|
|
Interface. For more information on how to identify your adapter,
|
|
go to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
More specific information on configuring the driver is in
|
|
<file:Documentation/networking/device_drivers/ethernet/intel/fm10k.rst>.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called fm10k. MSI-X interrupt support is required
|
|
|
|
config IGC
|
|
tristate "Intel(R) Ethernet Controller I225-LM/I225-V support"
|
|
default n
|
|
depends on PCI
|
|
help
|
|
This driver supports Intel(R) Ethernet Controller I225-LM/I225-V
|
|
family of adapters.
|
|
|
|
For more information on how to identify your adapter, go
|
|
to the Adapter & Driver ID Guide that can be located at:
|
|
|
|
<http://support.intel.com>
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called igc.
|
|
|
|
endif # NET_VENDOR_INTEL
|