Searched +full:dsa +full:- +full:specific (Results 1 – 25 of 118) sorted by relevance
12345
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| D | dsa.rst | 5 This document describes the **Distributed Switch Architecture (DSA)** subsystem
22 An Ethernet switch is typically comprised of multiple front-panel ports, and one
23 or more CPU or management port. The DSA subsystem currently relies on the
27 gateways, or even top-of-the rack switches. This host Ethernet controller will
28 be later referred to as "master" and "cpu" in DSA terminology and code.
30 The D in DSA stands for Distributed, because the subsystem has been designed
32 using upstream and downstream Ethernet links between switches. These specific
33 ports are referred to as "dsa" ports in DSA terminology and code. A collection
36 For each front-panel port, DSA will create specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
[all …]
|
| D | bcm_sf2.rst | 8 - xDSL gateways such as BCM63138
9 - streaming/multimedia Set Top Box such as BCM7445
10 - Cable Modem/residential gateways such as BCM7145/BCM3390
13 ports, offering a range of built-in and customizable interfaces:
15 - single integrated Gigabit PHY
16 - quad integrated Gigabit PHY
17 - quad external Gigabit PHY w/ MDIO multiplexer
18 - integrated MoCA PHY
19 - several external MII/RevMII/GMII/RGMII interfaces
21 The switch also supports specific congestion control features which allow MoCA
[all …]
|
| D | b53.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 The driver is located in ``drivers/net/dsa/b53/`` and is implemented as a
17 DSA driver; see ``Documentation/networking/dsa/dsa.rst`` for details on the
20 The switch is, if possible, configured to enable a Broadcom specific 4-bytes
24 ``net/dsa/tag_brcm.c``.
30 configuration described in the :ref:`dsa-config-showcases`.
33 ----------------------------------
35 The tagging based configuration is desired. It is not specific to the b53
36 DSA driver and will work like all DSA drivers which supports tagging.
38 See :ref:`dsa-tagged-configuration`.
[all …]
|
| D | lan9303.rst | 13 The driver is implemented as a DSA driver, see ``Documentation/networking/dsa/dsa.rst``.
15 See ``Documentation/devicetree/bindings/net/dsa/lan9303.txt`` for device tree
21 interfaces (which is the default state of a DSA device). Due to HW limitations,
36 - Support for VLAN filtering is not implemented
37 - The HW does not support VLAN-specific fdb entries
|
| /kernel/linux/linux-6.6/Documentation/networking/dsa/ |
| D | dsa.rst | 5 This document describes the **Distributed Switch Architecture (DSA)** subsystem
22 An Ethernet switch typically comprises multiple front-panel ports and one
23 or more CPU or management ports. The DSA subsystem currently relies on the
27 gateways, or even top-of-rack switches. This host Ethernet controller will
28 be later referred to as "master" and "cpu" in DSA terminology and code.
30 The D in DSA stands for Distributed, because the subsystem has been designed
32 using upstream and downstream Ethernet links between switches. These specific
33 ports are referred to as "dsa" ports in DSA terminology and code. A collection
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
[all …]
|
| D | bcm_sf2.rst | 8 - xDSL gateways such as BCM63138
9 - streaming/multimedia Set Top Box such as BCM7445
10 - Cable Modem/residential gateways such as BCM7145/BCM3390
13 ports, offering a range of built-in and customizable interfaces:
15 - single integrated Gigabit PHY
16 - quad integrated Gigabit PHY
17 - quad external Gigabit PHY w/ MDIO multiplexer
18 - integrated MoCA PHY
19 - several external MII/RevMII/GMII/RGMII interfaces
21 The switch also supports specific congestion control features which allow MoCA
[all …]
|
| D | b53.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 The driver is located in ``drivers/net/dsa/b53/`` and is implemented as a
17 DSA driver; see ``Documentation/networking/dsa/dsa.rst`` for details on the
20 The switch is, if possible, configured to enable a Broadcom specific 4-bytes
24 ``net/dsa/tag_brcm.c``.
30 configuration described in the :ref:`dsa-config-showcases`.
33 ----------------------------------
35 The tagging based configuration is desired. It is not specific to the b53
36 DSA driver and will work like all DSA drivers which supports tagging.
38 See :ref:`dsa-tagged-configuration`.
[all …]
|
| D | lan9303.rst | 13 The driver is implemented as a DSA driver, see ``Documentation/networking/dsa/dsa.rst``.
15 See ``Documentation/devicetree/bindings/net/dsa/lan9303.txt`` for device tree
21 interfaces (which is the default state of a DSA device). Due to HW limitations,
36 - Support for VLAN filtering is not implemented
37 - The HW does not support VLAN-specific fdb entries
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/dsa/ |
| D | dsa-port.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/dsa/dsa-port.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic DSA Switch Port
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Vladimir Oltean <olteanv@gmail.com>
15 A DSA switch port is a component of a switch that manages one MAC, and can
17 DSA-specific functionality.
[all …]
|
| D | marvell.txt | 1 Marvell DSA Switch Device Tree Bindings
2 ---------------------------------------
8 If you need a stable binding, use the old dsa.txt binding.
13 The properties described here are those specific to Marvell devices.
14 Additional required and optional properties can be found in dsa.txt.
18 - "marvell,mv88e6085" : Switch has base address 0x10. Use with models:
22 - "marvell,mv88e6190" : Switch has base address 0x00. Use with models:
24 - "marvell,mv88e6250" : Switch has base address 0x08 or 0x18. Use with model:
28 - compatible : Should be one of "marvell,mv88e6085",
31 - reg : Address on the MII bus for the switch.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/dsa/ |
| D | ocelot.txt | 5 -----
9 - VSC9959 (Felix)
10 - VSC9953 (Seville)
13 larger ENETC root complex. As a result, the ethernet-switch node is a sub-node
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
32 By default, in fsl-ls1028a.dtsi, the NPI port is assigned to the internal
33 2.5Gbps port@4, but can be moved to the 1Gbps port@5, depending on the specific
36 operate as an entire slave DSA chip. NPI functionality (and therefore DSA
39 Any port can be disabled (and in fsl-ls1028a.dtsi, they are indeed all disabled
[all …]
|
| D | marvell.txt | 1 Marvell DSA Switch Device Tree Bindings
2 ---------------------------------------
8 If you need a stable binding, use the old dsa.txt binding.
13 The properties described here are those specific to Marvell devices.
14 Additional required and optional properties can be found in dsa.txt.
18 - "marvell,mv88e6085" : Switch has base address 0x10. Use with models:
22 - "marvell,mv88e6190" : Switch has base address 0x00. Use with models:
24 - "marvell,mv88e6250" : Switch has base address 0x08 or 0x18. Use with model:
28 - compatible : Should be one of "marvell,mv88e6085",
31 - reg : Address on the MII bus for the switch.
[all …]
|
| /kernel/linux/linux-6.6/net/dsa/ |
| D | tag_dsa.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Regular and Ethertype DSA tagging
4 * Copyright (c) 2008-2009 Marvell Semiconductor
6 * Regular DSA
7 * -----------
12 * converted to a DSA tag. It expects the same layout when receiving
17 * .----.----.----.---------
19 * '----'----'----'---------
21 * .----.----.--------.-----.----.---------
23 * '----'----'--------'-----'----'---------
[all …]
|
| D | tag.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * DSA tagging protocol handling
5 * Copyright (c) 2008-2009 Marvell Semiconductor
13 #include <net/dsa.h>
26 * timestamp when it reads the packet out of the hardware. However in a DSA
27 * switch, the DSA driver owning the interface to which the packet is
33 struct dsa_switch *ds = p->dp->ds; in dsa_skb_defer_rx_timestamp()
36 if (!ds->ops->port_rxtstamp) in dsa_skb_defer_rx_timestamp()
51 return ds->ops->port_rxtstamp(ds, p->dp->index, skb, type); in dsa_skb_defer_rx_timestamp()
58 struct dsa_port *cpu_dp = dev->dsa_ptr; in dsa_switch_rcv()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | sja1105.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Driver-specific parameters implemented
16 * - Name
17 - Type
18 - Mode
19 - Description
20 * - ``best_effort_vlan_filtering``
21 - Boolean
22 - runtime
23 - Allow plain ETH_P_8021Q headers to be used as DSA tags.
[all …]
|
| /kernel/linux/linux-5.10/include/linux/platform_data/ |
| D | dsa.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
10 #define DSA_RTABLE_NONE -1
27 /* Device tree node pointer for this specific switch chip
36 * "dsa" to indicate that this port is a DSA link to
|
| /kernel/linux/linux-6.6/include/linux/platform_data/ |
| D | dsa.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
10 #define DSA_RTABLE_NONE -1
27 /* Device tree node pointer for this specific switch chip
36 * "dsa" to indicate that this port is a DSA link to
|
| /kernel/linux/linux-6.6/drivers/net/dsa/ocelot/ |
| D | felix.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
20 /* Platform-specific information */
49 * the extraction registers is triggered once the DSA tagger sees a PTP
69 /* Methods for initializing the hardware resources specific to a tagging
71 * for "ocelot-8021q").
87 /* DSA glue / front-end for struct ocelot */
|
| /kernel/linux/linux-5.10/include/net/ |
| D | dsa.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * include/net/dsa.h - Driver for Distributed Switch Architecture switch chips
4 * Copyright (c) 2008-2009 Marvell Semiconductor
20 #include <linux/platform_data/dsa.h>
79 /* Used to determine which traffic should match the DSA filter in
88 * address, in which case the DSA master would drop packets on ingress
97 * DSA layer on top of the DSA CPU/management net_device instance. This is
106 #define DSA_TAG_DRIVER_ALIAS "dsa_tag-"
116 u8 priv[48 - sizeof(struct dsa_skb_cb)];
119 #define DSA_SKB_CB(skb) ((struct dsa_skb_cb *)((skb)->cb))
[all …]
|
| /kernel/linux/linux-6.6/include/linux/dsa/ |
| D | brcm.h | 1 /* SPDX-License-Identifier: GPL-2.0-only
6 * net/dsa/tag_brcm.c
11 /* Broadcom tag specific helpers to insert and extract queue/port number */
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | timestamping.rst | 1 .. SPDX-License-Identifier: GPL-2.0
43 -------------------------------------------------------------
71 ----------------------------------------------------------------------
137 over-report measurement, because the timestamp is generated when all
179 is derived from a per-socket u32 counter (that wraps). For datagram
226 received the packet and its length at layer 2. A valid (non-zero)
261 cmsg->cmsg_level = SOL_SOCKET;
262 cmsg->cmsg_type = SO_TIMESTAMPING;
263 cmsg->cmsg_len = CMSG_LEN(sizeof(__u32));
281 -------------------------
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | timestamping.rst | 1 .. SPDX-License-Identifier: GPL-2.0
43 -------------------------------------------------------------
59 -------------------------------------------------------------------
72 ----------------------------------------------------------------------
138 over-report measurement, because the timestamp is generated when all
180 is derived from a per-socket u32 counter (that wraps). For datagram
207 a timestamp with counter N-1. SOF_TIMESTAMPING_OPT_ID_TCP
257 received the packet and its length at layer 2. A valid (non-zero)
292 cmsg->cmsg_level = SOL_SOCKET;
293 cmsg->cmsg_type = SO_TIMESTAMPING;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | syscon.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 represent as any specific type of device. The typical use-case is
13 for some other node's driver, or platform-specific code, to acquire
15 search using a specific compatible value), interrogate the node (or
20 - Lee Jones <lee.jones@linaro.org>
27 - syscon
30 - compatible
35 - items:
[all …]
|
| /kernel/linux/linux-6.6/drivers/scsi/sym53c8xx_2/ |
| D | sym_hipd.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
4 * of PCI-SCSI IO processors.
6 * Copyright (C) 1999-2001 Gerard Roudier <groudier@free.fr>
9 * Copyright (C) 1998-2000 Gerard Roudier
12 * a port of the FreeBSD ncr driver to Linux-1.2.13.
16 * Stefan Esser <se@mi.Uni-Koeln.de>
24 *-----------------------------------------------------------------------------
35 * They may be defined in platform specific headers, if they
55 * by the platform specific code to something else.
75 #define sym_verbose (np->verbose)
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/sym53c8xx_2/ |
| D | sym_hipd.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
4 * of PCI-SCSI IO processors.
6 * Copyright (C) 1999-2001 Gerard Roudier <groudier@free.fr>
9 * Copyright (C) 1998-2000 Gerard Roudier
12 * a port of the FreeBSD ncr driver to Linux-1.2.13.
16 * Stefan Esser <se@mi.Uni-Koeln.de>
24 *-----------------------------------------------------------------------------
35 * They may be defined in platform specific headers, if they
55 * by the platform specific code to something else.
75 #define sym_verbose (np->verbose)
[all …]
|
12345