Home
last modified time | relevance | path

Searched +full:ethernet +full:- +full:switch (Results 1 – 25 of 1044) sorted by relevance

12345678910>>...42

/kernel/linux/linux-5.10/drivers/net/dsa/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Distributed Switch Architecture drivers"
8 tristate "Broadcom Starfighter 2 Ethernet switch support"
16 This enables support for the Broadcom Starfighter 2 Ethernet
17 switch chips.
20 tristate "DSA mock-up Ethernet switch chip support"
24 This enables support for a fake mock-up switch chip which
36 tristate "MediaTek MT753x and MT7621 Ethernet switch support"
41 Ethernet switch chips.
44 tristate "Marvell 88E6060 ethernet switch chip support"
[all …]
/kernel/linux/linux-4.19/drivers/net/dsa/
DKconfig1 menu "Distributed Switch Architecture drivers"
7 tristate "Broadcom Starfighter 2 Ethernet switch support"
14 ---help---
15 This enables support for the Broadcom Starfighter 2 Ethernet
16 switch chips.
19 tristate "DSA mock-up Ethernet switch chip support"
22 ---help---
23 This enables support for a fake mock-up switch chip which
27 tristate "Mediatek MT7530 Ethernet switch support"
30 ---help---
[all …]
/kernel/linux/linux-5.10/Documentation/networking/dsa/
Ddsa.rst5 This document describes the **Distributed Switch Architecture (DSA)** subsystem
13 The Distributed Switch Architecture is a subsystem which was primarily designed
14 to support Marvell Ethernet switches (MV88E6xxx, a.k.a Linkstreet product line)
19 they configured/queried a switch port network device or a regular network
22 An Ethernet switch is typically comprised of multiple front-panel ports, and one
24 presence of a management port connected to an Ethernet controller capable of
25 receiving Ethernet frames from the switch. This is a very common setup for all
26 kinds of Ethernet switches found in Small Home and Office products: routers,
27 gateways, or even top-of-the rack switches. This host Ethernet controller will
32 using upstream and downstream Ethernet links between switches. These specific
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/dsa/
Ddsa.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Ethernet Switch Device Tree Bindings
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Vivien Didelot <vivien.didelot@gmail.com>
15 This binding represents Ethernet Switches which have a dedicated CPU
16 port. That port is usually connected to an Ethernet Controller of the
23 pattern: "^switch(@.*)?$"
[all …]
Dvitesse,vsc73xx.txt4 This defines device tree bindings for the Vitesse VSC73xx switch chips.
8 The currently supported switch chips are:
9 Vitesse VSC7385 SparX-G5 5+1-port Integrated Gigabit Ethernet Switch
10 Vitesse VSC7388 SparX-G8 8-port Integrated Gigabit Ethernet Switch
11 Vitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet Switch
12 Vitesse VSC7398 SparX-G8e 8-port Integrated Gigabit Ethernet Switch
14 This switch could have two different management interface.
17 reside inside a SPI bus device tree node, see spi/spi-bus.txt
19 When the chip is connected to a parallel memory bus and work in memory-mapped
25 - compatible: must be exactly one of:
[all …]
Docelot.txt1 Microchip Ocelot switch driver family
5 -----
9 - VSC9959 (Felix)
10 - VSC9953 (Seville)
12 The VSC9959 switch is found in the NXP LS1028A. It is a PCI device, part of the
13 larger ENETC root complex. As a result, the ethernet-switch node is a sub-node
18 in this case for the Ethernet L2Switch it is PF5 (of device 0, bus 0).
25 For the external switch ports, depending on board configuration, "phy-mode" and
26 "phy-handle" are populated by board specific device tree instances. Ports 4 and
29 The CPU port property ("ethernet") configures the feature called "NPI port" in
[all …]
Db53.txt1 Broadcom BCM53xx Ethernet switches
6 - compatible: For external switch chips, compatible string must be exactly one
18 "brcm,bcm11360-srab" and the mandatory "brcm,cygnus-srab" string
20 For the BCM5310x SoCs with an integrated switch, must be one of:
21 "brcm,bcm53010-srab"
22 "brcm,bcm53011-srab"
23 "brcm,bcm53012-srab"
24 "brcm,bcm53018-srab"
25 "brcm,bcm53019-srab" and the mandatory "brcm,bcm5301x-srab" string
27 For the BCM5831X/BCM1140x SoCs with an integrated switch, must be one of:
[all …]
/kernel/linux/linux-4.19/Documentation/networking/dsa/
Ddsa.txt1 Distributed Switch Architecture
7 This document describes the Distributed Switch Architecture (DSA) subsystem
15 The Distributed Switch Architecture is a subsystem which was primarily designed
16 to support Marvell Ethernet switches (MV88E6xxx, a.k.a Linkstreet product line)
21 they configured/queried a switch port network device or a regular network
24 An Ethernet switch is typically comprised of multiple front-panel ports, and one
26 presence of a management port connected to an Ethernet controller capable of
27 receiving Ethernet frames from the switch. This is a very common setup for all
28 kinds of Ethernet switches found in Small Home and Office products: routers,
29 gateways, or even top-of-the rack switches. This host Ethernet controller will
[all …]
/kernel/linux/linux-4.19/Documentation/infiniband/
Dopa_vnic.txt1 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC) feature
2 supports Ethernet functionality over Omni-Path fabric by encapsulating
3 the Ethernet packets between HFI nodes.
7 The patterns of exchanges of Omni-Path encapsulated Ethernet packets
8 involves one or more virtual Ethernet switches overlaid on the Omni-Path
9 fabric topology. A subset of HFI nodes on the Omni-Path fabric are
10 permitted to exchange encapsulated Ethernet packets across a particular
11 virtual Ethernet switch. The virtual Ethernet switches are logical
14 nodes across the fabric exchange encapsulated Ethernet packets over a
15 single virtual Ethernet switch. A virtual Ethernet switch, is effectively
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/
Dkeystone-netcp.txt5 Ethernet packets. NetCP has a gigabit Ethernet (GbE) subsystem with a ethernet
6 switch sub-module to send and receive packets. NetCP also includes a packet
12 Keystone II SoC's also have a 10 Gigabit Ethernet Subsystem (XGbE) which
13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates
14 per Ethernet port.
16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
17 sub-modules exist as a loadable kernel module which plug in to the netcp core.
18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is
19 mandatory to have the ethernet switch sub-module for the ethernet interface to
20 be operational. Any other sub-module like the PA is optional.
[all …]
/kernel/linux/linux-5.10/drivers/net/ethernet/ti/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
11 If you have a network (Ethernet) card belonging to this class, say Y.
27 This driver supports TI's DaVinci Ethernet .
50 tristate "TI CPSW Switch Support"
59 This driver supports TI's CPSW Ethernet Switch.
65 tristate "TI CPSW Switch Support with switchdev"
76 This driver supports TI's CPSW Ethernet Switch.
88 the CPSW Ethernet Switch and Keystone 2 1g/10g Switch Subsystem.
93 tristate "TI K3 AM654x/J721E CPSW Ethernet driver"
99 This driver supports TI K3 AM654/J721E CPSW2G Ethernet SubSystem.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dkeystone-netcp.txt5 Ethernet packets. NetCP has a gigabit Ethernet (GbE) subsystem with a ethernet
6 switch sub-module to send and receive packets. NetCP also includes a packet
12 Keystone II SoC's also have a 10 Gigabit Ethernet Subsystem (XGbE) which
13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates
14 per Ethernet port.
16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
17 sub-modules exist as a loadable kernel module which plug in to the netcp core.
18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is
19 mandatory to have the ethernet switch sub-module for the ethernet interface to
20 be operational. Any other sub-module like the PA is optional.
[all …]
Dti,cpsw-switch.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/ti,cpsw-switch.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI SoC Ethernet Switch Controller (CPSW) Device Tree Bindings
10 - Grygorii Strashko <grygorii.strashko@ti.com>
11 - Sekhar Nori <nsekhar@ti.com>
14 The 3-port switch gigabit ethernet subsystem provides ethernet packet
15 communication and can be configured as an ethernet switch. It provides the
24 - const: ti,cpsw-switch
[all …]
Dmdio-mux.txt1 Common MDIO bus multiplexer/switch properties.
3 An MDIO bus multiplexer/switch will have several child busses that are
5 bus multiplexer/switch will have one child node for each child bus.
8 - #address-cells = <1>;
9 - #size-cells = <0>;
12 - mdio-parent-bus : phandle to the parent MDIO bus.
14 - Other properties specific to the multiplexer/switch hardware.
17 - #address-cells = <1>;
18 - #size-cells = <0>;
19 - reg : The sub-bus number.
[all …]
/kernel/linux/linux-5.10/Documentation/infiniband/
Dopa_vnic.rst2 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC)
5 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC) feature
6 supports Ethernet functionality over Omni-Path fabric by encapsulating
7 the Ethernet packets between HFI nodes.
11 The patterns of exchanges of Omni-Path encapsulated Ethernet packets
12 involves one or more virtual Ethernet switches overlaid on the Omni-Path
13 fabric topology. A subset of HFI nodes on the Omni-Path fabric are
14 permitted to exchange encapsulated Ethernet packets across a particular
15 virtual Ethernet switch. The virtual Ethernet switches are logical
18 nodes across the fabric exchange encapsulated Ethernet packets over a
[all …]
/kernel/linux/linux-4.19/drivers/infiniband/ulp/opa_vnic/
Dopa_vnic_encap.h26 * - Redistributions of source code must retain the above copyright
28 * - Redistributions in binary form must reproduce the above copyright
32 * - Neither the name of Intel Corporation nor the names of its
52 * and decapsulation of Ethernet packets
63 * ETHERNET MANAGEMENT
84 #define OPA_VNIC_EMA_DATA (OPA_MGMT_MAD_SIZE - IB_MGMT_VENDOR_HDR)
102 /* VNIC Ethernet link status */
118 * struct opa_vesw_info - OPA vnic switch information
119 * @fabric_id: 10-bit fabric id
120 * @vesw_id: 12-bit virtual ethernet switch id
[all …]
/kernel/linux/linux-5.10/drivers/net/dsa/sja1105/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "NXP SJA1105 Ethernet switch family support"
9 This is the driver for the NXP SJA1105 automotive Ethernet switch
10 family. These are 5-port devices and are managed over an SPI
13 - SJA1105E (Gen. 1, No TT-Ethernet)
14 - SJA1105T (Gen. 1, TT-Ethernet)
15 - SJA1105P (Gen. 2, No SGMII, No TT-Ethernet)
16 - SJA1105Q (Gen. 2, No SGMII, TT-Ethernet)
17 - SJA1105R (Gen. 2, SGMII, No TT-Ethernet)
18 - SJA1105S (Gen. 2, SGMII, TT-Ethernet)
[all …]
/kernel/linux/linux-4.19/drivers/staging/fsl-dpaa2/ethsw/
DREADME1 DPAA2 Ethernet Switch driver
4 This file provides documentation for the DPAA2 Ethernet Switch driver
11 Creating an Ethernet Switch
23 The Ethernet Switch in the DPAA2 architecture consists of several hardware
31 drivers/staging/fsl-mc/README.txt
33 The Ethernet Switch is built on top of a Datapath Switch (DPSW) object.
37 ---------------------
38 | DPAA2 Switch driver |
39 ---------------------
42 ----------
[all …]
/kernel/linux/linux-5.10/drivers/staging/fsl-dpaa2/ethsw/
DREADME1 DPAA2 Ethernet Switch driver
4 This file provides documentation for the DPAA2 Ethernet Switch driver
11 Creating an Ethernet Switch
23 The Ethernet Switch in the DPAA2 architecture consists of several hardware
31 drivers/staging/fsl-mc/README.txt
33 The Ethernet Switch is built on top of a Datapath Switch (DPSW) object.
37 ---------------------
38 | DPAA2 Switch driver |
39 ---------------------
42 ----------
[all …]
/kernel/linux/linux-5.10/drivers/infiniband/ulp/opa_vnic/
Dopa_vnic_encap.h26 * - Redistributions of source code must retain the above copyright
28 * - Redistributions in binary form must reproduce the above copyright
32 * - Neither the name of Intel Corporation nor the names of its
52 * and decapsulation of Ethernet packets
63 * ETHERNET MANAGEMENT
84 #define OPA_VNIC_EMA_DATA (OPA_MGMT_MAD_SIZE - IB_MGMT_VENDOR_HDR)
102 /* VNIC Ethernet link status */
118 * struct opa_vesw_info - OPA vnic switch information
119 * @fabric_id: 10-bit fabric id
120 * @vesw_id: 12-bit virtual ethernet switch id
[all …]
/kernel/linux/linux-4.19/drivers/net/ethernet/mellanox/mlx5/core/
DKconfig13 ---help---
14 Core driver for low level functionality of the ConnectX-4 and
15 Connect-IB cards by Mellanox Technologies.
24 ---help---
29 sandbox-specific client drivers.
32 bool "Mellanox 5th generation network adapters (ConnectX series) Ethernet support"
33 depends on NETDEVICES && ETHERNET && INET && PCI && MLX5_CORE
37 ---help---
38 Ethernet support in Mellanox Technologies ConnectX-4 NIC.
41 bool "Mellanox MLX5 ethernet accelerated receive flow steering (ARFS) support"
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/dsa/
Ddsa.txt1 Distributed Switch Architecture Device Tree Bindings
2 ----------------------------------------------------
8 ---------------
18 - ports : A container for child nodes representing switch ports.
22 - dsa,member : A two element list indicates which DSA cluster, and position
23 within the cluster a switch takes. <0 0> is cluster 0,
24 switch 0. <0 1> is cluster 0, switch 1. <1 0> is cluster 1,
25 switch 0. A switch not part of any cluster (single device
32 - #address-cells : Must be 1
33 - #size-cells : Must be 0
[all …]
Db53.txt1 Broadcom BCM53xx Ethernet switches
6 - compatible: For external switch chips, compatible string must be exactly one
18 "brcm,bcm11360-srab" and the mandatory "brcm,cygnus-srab" string
20 For the BCM5310x SoCs with an integrated switch, must be one of:
21 "brcm,bcm53010-srab"
22 "brcm,bcm53011-srab"
23 "brcm,bcm53012-srab"
24 "brcm,bcm53018-srab"
25 "brcm,bcm53019-srab" and the mandatory "brcm,bcm5301x-srab" string
27 For the BCM5831X/BCM1140x SoCs with an integrated switch, must be one of:
[all …]
Dvitesse,vsc73xx.txt4 This defines device tree bindings for the Vitesse VSC73xx switch chips.
8 The currently supported switch chips are:
9 Vitesse VSC7385 SparX-G5 5+1-port Integrated Gigabit Ethernet Switch
10 Vitesse VSC7388 SparX-G8 8-port Integrated Gigabit Ethernet Switch
11 Vitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet Switch
12 Vitesse VSC7398 SparX-G8e 8-port Integrated Gigabit Ethernet Switch
15 device tree node, see spi/spi-bus.txt
19 - compatible: must be exactly one of:
24 - gpio-controller: indicates that this switch is also a GPIO controller,
26 - #gpio-cells: this must be set to <2> and indicates that we are a twocell
[all …]
/kernel/linux/linux-4.19/drivers/net/ethernet/ti/
DKconfig9 ---help---
10 If you have a network (Ethernet) card belonging to this class, say Y.
25 ---help---
26 This driver supports TI's DaVinci Ethernet .
35 ---help---
45 ---help---
53 ---help---
59 ---help---
63 tristate "TI CPSW Switch Support"
71 ---help---
[all …]

12345678910>>...42