mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
9ed4050c0d
Add XDP support based on rx page_pool allocator, one frame per page. Page pool allocator is used with assumption that only one rx_handler is running simultaneously. DMA map/unmap is reused from page pool despite there is no need to map whole page. Due to specific of cpsw, the same TX/RX handler can be used by 2 network devices, so special fields in buffer are added to identify an interface the frame is destined to. Thus XDP works for both interfaces, that allows to test xdp redirect between two interfaces easily. Also, each rx queue have own page pools, but common for both netdevs. XDP prog is common for all channels till appropriate changes are added in XDP infrastructure. Also, once page_pool recycling becomes part of skb netstack some simplifications can be added, like removing page_pool_release_page() before skb receive. In order to keep rx_dev while redirect, that can be somehow used in future, do flush in rx_handler, that allows to keep rx dev the same while redirect. It allows to conform with tracing rx_dev pointed by Jesper. Also, there is probability, that XDP generic code can be extended to support multi ndev drivers like this one, using same rx queue for several ndevs, based on switchdev for instance or else. In this case, driver can be modified like exposed here: https://lkml.org/lkml/2019/7/3/243 Acked-by: Jesper Dangaard Brouer <brouer@redhat.com> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org> Signed-off-by: David S. Miller <davem@davemloft.net>
124 lines
3.6 KiB
Plaintext
124 lines
3.6 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# TI device configuration
|
|
#
|
|
|
|
config NET_VENDOR_TI
|
|
bool "Texas Instruments (TI) devices"
|
|
default y
|
|
depends on PCI || EISA || AR7 || ARCH_DAVINCI || ARCH_OMAP2PLUS || ARCH_KEYSTONE
|
|
---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 TI devices. If you say Y, you will be asked for
|
|
your specific card in the following questions.
|
|
|
|
if NET_VENDOR_TI
|
|
|
|
config TI_DAVINCI_EMAC
|
|
tristate "TI DaVinci EMAC Support"
|
|
depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) || COMPILE_TEST
|
|
select TI_DAVINCI_MDIO
|
|
select PHYLIB
|
|
---help---
|
|
This driver supports TI's DaVinci Ethernet .
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called davinci_emac_driver. This is recommended.
|
|
|
|
config TI_DAVINCI_MDIO
|
|
tristate "TI DaVinci MDIO Support"
|
|
depends on ARCH_DAVINCI || ARCH_OMAP2PLUS || ARCH_KEYSTONE || COMPILE_TEST
|
|
select PHYLIB
|
|
---help---
|
|
This driver supports TI's DaVinci MDIO module.
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called davinci_mdio. This is recommended.
|
|
|
|
config TI_CPSW_PHY_SEL
|
|
bool "TI CPSW Phy mode Selection (DEPRECATED)"
|
|
default n
|
|
---help---
|
|
This driver supports configuring of the phy mode connected to
|
|
the CPSW. DEPRECATED: use PHY_TI_GMII_SEL.
|
|
|
|
config TI_CPSW
|
|
tristate "TI CPSW Switch Support"
|
|
depends on ARCH_DAVINCI || ARCH_OMAP2PLUS || COMPILE_TEST
|
|
select TI_DAVINCI_MDIO
|
|
select MFD_SYSCON
|
|
select PAGE_POOL
|
|
select REGMAP
|
|
---help---
|
|
This driver supports TI's CPSW Ethernet Switch.
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called cpsw.
|
|
|
|
config TI_CPTS
|
|
bool "TI Common Platform Time Sync (CPTS) Support"
|
|
depends on TI_CPSW || TI_KEYSTONE_NETCP || COMPILE_TEST
|
|
depends on COMMON_CLK
|
|
depends on POSIX_TIMERS
|
|
---help---
|
|
This driver supports the Common Platform Time Sync unit of
|
|
the CPSW Ethernet Switch and Keystone 2 1g/10g Switch Subsystem.
|
|
The unit can time stamp PTP UDP/IPv4 and Layer 2 packets, and the
|
|
driver offers a PTP Hardware Clock.
|
|
|
|
config TI_CPTS_MOD
|
|
tristate
|
|
depends on TI_CPTS
|
|
default y if TI_CPSW=y || TI_KEYSTONE_NETCP=y
|
|
select NET_PTP_CLASSIFY
|
|
imply PTP_1588_CLOCK
|
|
default m
|
|
|
|
config TI_KEYSTONE_NETCP
|
|
tristate "TI Keystone NETCP Core Support"
|
|
select TI_DAVINCI_MDIO
|
|
depends on OF
|
|
depends on KEYSTONE_NAVIGATOR_DMA && KEYSTONE_NAVIGATOR_QMSS
|
|
---help---
|
|
This driver supports TI's Keystone NETCP Core.
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called keystone_netcp.
|
|
|
|
config TI_KEYSTONE_NETCP_ETHSS
|
|
depends on TI_KEYSTONE_NETCP
|
|
tristate "TI Keystone NETCP Ethernet subsystem Support"
|
|
---help---
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
will be called keystone_netcp_ethss.
|
|
|
|
config TLAN
|
|
tristate "TI ThunderLAN support"
|
|
depends on (PCI || EISA)
|
|
---help---
|
|
If you have a PCI Ethernet network card based on the ThunderLAN chip
|
|
which is supported by this driver, say Y here.
|
|
|
|
Devices currently supported by this driver are Compaq Netelligent,
|
|
Compaq NetFlex and Olicom cards. Please read the file
|
|
<file:Documentation/networking/device_drivers/ti/tlan.txt>
|
|
for more details.
|
|
|
|
To compile this driver as a module, choose M here. The module
|
|
will be called tlan.
|
|
|
|
Please email feedback to <torben.mathiasen@compaq.com>.
|
|
|
|
config CPMAC
|
|
tristate "TI AR7 CPMAC Ethernet support"
|
|
depends on AR7
|
|
select PHYLIB
|
|
---help---
|
|
TI AR7 CPMAC Ethernet support
|
|
|
|
endif # NET_VENDOR_TI
|