2019-05-19 20:07:45 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2011-06-11 17:29:36 +08:00
|
|
|
#
|
|
|
|
|
# Freescale device configuration
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
config NET_VENDOR_FREESCALE
|
|
|
|
|
bool "Freescale devices"
|
2011-08-23 16:29:52 +08:00
|
|
|
default y
|
2011-06-11 17:29:36 +08:00
|
|
|
depends on FSL_SOC || QUICC_ENGINE || CPM1 || CPM2 || PPC_MPC512x || \
|
|
|
|
|
M523x || M527x || M5272 || M528x || M520x || M532x || \
|
2015-11-20 11:54:08 +08:00
|
|
|
ARCH_MXC || ARCH_MXS || (PPC_MPC52xx && PPC_BESTCOMM) || \
|
2016-11-18 03:19:11 +08:00
|
|
|
ARCH_LAYERSCAPE || COMPILE_TEST
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2015-06-22 04:28:02 +08:00
|
|
|
If you have a network (Ethernet) card belonging to this class, say Y.
|
2011-06-11 17:29:36 +08:00
|
|
|
|
|
|
|
|
Note that the answer to this question doesn't directly affect the
|
|
|
|
|
kernel: saying N will just cause the configurator to skip all
|
2011-09-23 10:12:48 +08:00
|
|
|
the questions about Freescale devices. If you say Y, you will be
|
|
|
|
|
asked for your specific card in the following questions.
|
2011-06-11 17:29:36 +08:00
|
|
|
|
|
|
|
|
if NET_VENDOR_FREESCALE
|
|
|
|
|
|
|
|
|
|
config FEC
|
2011-12-08 05:59:32 +08:00
|
|
|
tristate "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
|
2011-06-11 17:29:36 +08:00
|
|
|
depends on (M523x || M527x || M5272 || M528x || M520x || M532x || \
|
2018-05-18 04:07:44 +08:00
|
|
|
ARCH_MXC || SOC_IMX28 || COMPILE_TEST)
|
2012-01-03 11:46:47 +08:00
|
|
|
default ARCH_MXC || SOC_IMX28 if ARM
|
ethernet: fix PTP_1588_CLOCK dependencies
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>
2021-08-13 02:33:58 +08:00
|
|
|
depends on PTP_1588_CLOCK_OPTIONAL
|
2020-12-04 07:20:37 +08:00
|
|
|
select CRC32
|
2011-06-11 17:29:36 +08:00
|
|
|
select PHYLIB
|
2021-04-28 21:09:46 +08:00
|
|
|
imply NET_SELFTESTS
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2011-06-11 17:29:36 +08:00
|
|
|
Say Y here if you want to use the built-in 10/100 Fast ethernet
|
|
|
|
|
controller on some Motorola ColdFire and Freescale i.MX processors.
|
|
|
|
|
|
|
|
|
|
config FEC_MPC52xx
|
|
|
|
|
tristate "FEC MPC52xx driver"
|
|
|
|
|
depends on PPC_MPC52xx && PPC_BESTCOMM
|
|
|
|
|
select CRC32
|
|
|
|
|
select PHYLIB
|
|
|
|
|
select PPC_BESTCOMM_FEC
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2011-06-11 17:29:36 +08:00
|
|
|
This option enables support for the MPC5200's on-chip
|
|
|
|
|
Fast Ethernet Controller
|
|
|
|
|
If compiled as module, it will be called fec_mpc52xx.
|
|
|
|
|
|
|
|
|
|
config FEC_MPC52xx_MDIO
|
|
|
|
|
bool "FEC MPC52xx MDIO bus driver"
|
|
|
|
|
depends on FEC_MPC52xx
|
|
|
|
|
default y
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2011-06-11 17:29:36 +08:00
|
|
|
The MPC5200's FEC can connect to the Ethernet either with
|
|
|
|
|
an external MII PHY chip or 10 Mbps 7-wire interface
|
|
|
|
|
(Motorola? industry standard).
|
|
|
|
|
If your board uses an external PHY connected to FEC, enable this.
|
|
|
|
|
If not sure, enable.
|
|
|
|
|
If compiled as module, it will be called fec_mpc52xx_phy.
|
|
|
|
|
|
|
|
|
|
source "drivers/net/ethernet/freescale/fs_enet/Kconfig"
|
2015-12-21 08:21:25 +08:00
|
|
|
source "drivers/net/ethernet/freescale/fman/Kconfig"
|
2011-06-11 17:29:36 +08:00
|
|
|
|
|
|
|
|
config FSL_PQ_MDIO
|
|
|
|
|
tristate "Freescale PQ MDIO"
|
|
|
|
|
select PHYLIB
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2011-06-11 17:29:36 +08:00
|
|
|
This driver supports the MDIO bus used by the gianfar and UCC drivers.
|
|
|
|
|
|
2012-08-20 17:26:39 +08:00
|
|
|
config FSL_XGMAC_MDIO
|
|
|
|
|
tristate "Freescale XGMAC MDIO"
|
|
|
|
|
select PHYLIB
|
2016-11-18 03:19:11 +08:00
|
|
|
depends on OF
|
2014-06-12 02:48:17 +08:00
|
|
|
select OF_MDIO
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2015-01-04 17:36:02 +08:00
|
|
|
This driver supports the MDIO bus on the Fman 10G Ethernet MACs, and
|
|
|
|
|
on the FMan mEMAC (which supports both Clauses 22 and 45)
|
2012-08-20 17:26:39 +08:00
|
|
|
|
2011-06-11 17:29:36 +08:00
|
|
|
config UCC_GETH
|
|
|
|
|
tristate "Freescale QE Gigabit Ethernet"
|
2019-11-28 22:55:52 +08:00
|
|
|
depends on QUICC_ENGINE && PPC32
|
2011-06-11 17:29:36 +08:00
|
|
|
select FSL_PQ_MDIO
|
|
|
|
|
select PHYLIB
|
2020-05-09 20:04:52 +08:00
|
|
|
select FIXED_PHY
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2011-06-11 17:29:36 +08:00
|
|
|
This driver supports the Gigabit Ethernet mode of the QUICC Engine,
|
|
|
|
|
which is available on some Freescale SOCs.
|
|
|
|
|
|
|
|
|
|
config UGETH_TX_ON_DEMAND
|
|
|
|
|
bool "Transmit on Demand support"
|
|
|
|
|
depends on UCC_GETH
|
|
|
|
|
|
|
|
|
|
config GIANFAR
|
|
|
|
|
tristate "Gianfar Ethernet"
|
2016-11-18 03:19:11 +08:00
|
|
|
depends on HAS_DMA
|
2011-06-11 17:29:36 +08:00
|
|
|
select FSL_PQ_MDIO
|
|
|
|
|
select PHYLIB
|
2020-05-09 20:04:52 +08:00
|
|
|
select FIXED_PHY
|
2011-06-11 17:29:36 +08:00
|
|
|
select CRC32
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2011-06-11 17:29:36 +08:00
|
|
|
This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
|
2015-06-25 11:34:38 +08:00
|
|
|
and MPC86xx family of chips, the eTSEC on LS1021A and the FEC
|
|
|
|
|
on the 8540.
|
2011-06-11 17:29:36 +08:00
|
|
|
|
2016-11-15 16:41:02 +08:00
|
|
|
source "drivers/net/ethernet/freescale/dpaa/Kconfig"
|
2018-10-08 15:44:25 +08:00
|
|
|
source "drivers/net/ethernet/freescale/dpaa2/Kconfig"
|
enetc: Introduce basic PF and VF ENETC ethernet drivers
ENETC is a multi-port virtualized Ethernet controller supporting GbE
designs and Time-Sensitive Networking (TSN) functionality.
ENETC is operating as an SR-IOV multi-PF capable Root Complex Integrated
Endpoint (RCIE). As such, it contains multiple physical (PF) and
virtual (VF) PCIe functions, discoverable by standard PCI Express.
Introduce basic PF and VF ENETC ethernet drivers. The PF has access to
the ENETC Port registers and resources and makes the required privileged
configurations for the underlying VF devices. Common functionality is
controlled through so called System Interface (SI) register blocks, PFs
and VFs own a SI each. Though SI register blocks are almost identical,
there are a few privileged SI level controls that are accessible only to
PFs, and so the distinction is made between PF SIs (PSI) and VF SIs (VSI).
As such, the bulk of the code, including datapath processing, basic h/w
offload support and generic pci related configuration, is shared between
the 2 drivers and is factored out in common source files (i.e. enetc.c).
Major functionalities included (for both drivers):
MSI-X support for Rx and Tx processing, assignment of Rx/Tx BD ring pairs
to MSI-X entries, multi-queue support, Rx S/G (Rx frame fragmentation) and
jumbo frame (up to 9600B) support, Rx paged allocation and reuse, Tx S/G
support (NETIF_F_SG), Rx and Tx checksum offload, PF MAC filtering and
initial control ring support, VLAN extraction/ insertion, PF Rx VLAN
CTAG filtering, VF mac address config support, VF VLAN isolation support,
etc.
Signed-off-by: Claudiu Manoil <claudiu.manoil@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2019-01-22 21:29:54 +08:00
|
|
|
source "drivers/net/ethernet/freescale/enetc/Kconfig"
|
2018-08-29 17:42:40 +08:00
|
|
|
|
2011-06-11 17:29:36 +08:00
|
|
|
endif # NET_VENDOR_FREESCALE
|