| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-driver-dma-idxd | 1 What: /sys/bus/dsa/devices/dsa<m>/version 7 What: /sys/bus/dsa/devices/dsa<m>/cdev_major 14 What: /sys/bus/dsa/devices/dsa<m>/errors 20 What: /sys/bus/dsa/devices/dsa<m>/max_batch_size 26 What: /sys/bus/dsa/devices/dsa<m>/max_work_queues_size 32 What: /sys/bus/dsa/devices/dsa<m>/max_engines 38 What: /sys/bus/dsa/devices/dsa<m>/max_groups 44 What: /sys/bus/dsa/devices/dsa<m>/max_tokens 49 The bandwidth tokens represent resources within the DSA 53 What: /sys/bus/dsa/devices/dsa<m>/max_transfer_size [all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/stable/ |
| D | sysfs-driver-dma-idxd | 1 What: /sys/bus/dsa/devices/dsa<m>/version 7 What: /sys/bus/dsa/devices/dsa<m>/cdev_major 14 What: /sys/bus/dsa/devices/dsa<m>/errors 20 What: /sys/bus/dsa/devices/dsa<m>/max_batch_size 27 What: /sys/bus/dsa/devices/dsa<m>/max_work_queues_size 33 What: /sys/bus/dsa/devices/dsa<m>/max_engines 39 What: /sys/bus/dsa/devices/dsa<m>/max_groups 45 What: /sys/bus/dsa/devices/dsa<m>/max_read_buffers 50 The read buffers represent resources within the DSA 52 support operations. See DSA spec v1.2 9.2.4 Total Read Buffers. [all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/dsa/ |
| D | dsa.rst | 5 This document describes the **Distributed Switch Architecture (DSA)** subsystem 23 or more CPU or management ports. The DSA subsystem currently relies on the 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 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 39 interfaces in DSA terminology and code. 41 The ideal case for using DSA is when an Ethernet switch supports a "switch tag" 54 Note that DSA does not currently create network interfaces for the "cpu" and 55 "dsa" ports because: [all …]
|
| D | configuration.rst | 4 DSA switch configuration from userspace 7 The DSA switch configuration is not integrated into the main userspace 15 To configure a DSA switch a couple of commands need to be executed. In this 32 Through DSA every port of a switch is handled like a normal linux Ethernet 42 - when a DSA slave interface is brought up, the master interface is 44 - when the master interface is brought down, all DSA slave interfaces are 88 DSA switches. These switches are capable to tag incoming and outgoing traffic 302 The existing DSA switches do not have the necessary hardware support to keep 308 Up until kernel v4.14, DSA only supported user space management of bridge FDB 319 Due to a bug, the bridge bypass FDB implementation provided by DSA did not [all …]
|
| D | bcm_sf2.rst | 41 The driver is located in ``drivers/net/dsa/bcm_sf2.c`` and is implemented as a DSA 42 driver; see ``Documentation/networking/dsa/dsa.rst`` for details on the subsystem 49 ``net/dsa/tag_brcm.c``. 51 Overall, the SF2 driver is a fairly regular DSA driver; there are a few 57 The DSA platform device driver is probed using a specific compatible string 58 provided in ``net/dsa/dsa.c``. The reason for that is because the DSA subsystem gets 59 registered as a platform device driver currently. DSA will provide the needed 70 Broadcom switches connected to a SF2 require the use of the DSA slave MDIO bus 74 "double" programming. Using DSA, and setting ``ds->phys_mii_mask`` accordingly, we
|
| D | b53.rst | 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 24 ``net/dsa/tag_brcm.c``. 30 configuration described in the :ref:`dsa-config-showcases`. 36 DSA driver and will work like all DSA drivers which supports tagging. 38 See :ref:`dsa-tagged-configuration`. 48 The configuration slightly differ from the :ref:`dsa-vlan-configuration`. 54 In difference to the configuration described in :ref:`dsa-vlan-configuration`
|
| 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,
|
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| D | dsa.rst | 5 This document describes the **Distributed Switch Architecture (DSA)** subsystem 23 or more CPU or management port. The DSA subsystem currently relies on the 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 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 39 interfaces in DSA terminology and code. 41 The ideal case for using DSA is when an Ethernet switch supports a "switch tag" 54 Note that DSA does not currently create network interfaces for the "cpu" and 55 "dsa" ports because: [all …]
|
| D | bcm_sf2.rst | 41 The driver is located in ``drivers/net/dsa/bcm_sf2.c`` and is implemented as a DSA 42 driver; see ``Documentation/networking/dsa/dsa.rst`` for details on the subsystem 49 ``net/dsa/tag_brcm.c``. 51 Overall, the SF2 driver is a fairly regular DSA driver; there are a few 57 The DSA platform device driver is probed using a specific compatible string 58 provided in ``net/dsa/dsa.c``. The reason for that is because the DSA subsystem gets 59 registered as a platform device driver currently. DSA will provide the needed 70 Broadcom switches connected to a SF2 require the use of the DSA slave MDIO bus 74 "double" programming. Using DSA, and setting ``ds->phys_mii_mask`` accordingly, we
|
| D | b53.rst | 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 24 ``net/dsa/tag_brcm.c``. 30 configuration described in the :ref:`dsa-config-showcases`. 36 DSA driver and will work like all DSA drivers which supports tagging. 38 See :ref:`dsa-tagged-configuration`. 48 The configuration slightly differ from the :ref:`dsa-vlan-configuration`. 54 In difference to the configuration described in :ref:`dsa-vlan-configuration`
|
| 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,
|
| /kernel/linux/linux-5.10/scripts/coccinelle/api/debugfs/ |
| D | debugfs_simple_attr.cocci | 18 @dsa@ 28 identifier dsa.dsa_fops; 35 identifier dsa.dsa_fops; 36 expression dsa.dsa_get, dsa.dsa_set, dsa.dsa_fmt; 43 identifier dsa.dsa_fops; 49 identifier dsa.dsa_fops; 50 expression dsa.dsa_get, dsa.dsa_set, dsa.dsa_fmt; 57 fops << dsa.dsa_fops; 58 p << dsa.p; 64 fops << dsa.dsa_fops; [all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/ |
| D | brcm,bcm7445-switch-v4.0.txt | 3 See dsa/brcm,bcm7445-switch-v4.0.yaml for the documentation. 7 - dsa,mii-bus: phandle to the MDIO bus controller, see dsa/dsa.txt 8 - dsa,ethernet: phandle to the CPU network interface controller, see dsa/dsa.txt 9 - #address-cells: must be 2, see dsa/dsa.txt 11 Example using the old DSA DeviceTree binding:
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/marvell/prestera/ |
| D | prestera_dsa.c | 34 int prestera_dsa_parse(struct prestera_dsa *dsa, const u8 *dsa_buf) in prestera_dsa_parse() argument 62 dsa->vlan.is_tagged = FIELD_GET(PRESTERA_DSA_W0_IS_TAGGED, words[0]); in prestera_dsa_parse() 63 dsa->vlan.cfi_bit = FIELD_GET(PRESTERA_DSA_W1_CFI_BIT, words[1]); in prestera_dsa_parse() 64 dsa->vlan.vpt = FIELD_GET(PRESTERA_DSA_W0_VPT, words[0]); in prestera_dsa_parse() 65 dsa->vlan.vid = FIELD_GET(PRESTERA_DSA_W0_VID, words[0]); in prestera_dsa_parse() 66 dsa->vlan.vid &= ~PRESTERA_DSA_VID; in prestera_dsa_parse() 67 dsa->vlan.vid |= FIELD_PREP(PRESTERA_DSA_VID, field); in prestera_dsa_parse() 71 dsa->hw_dev_num = FIELD_GET(PRESTERA_DSA_W0_DEV_NUM, words[0]); in prestera_dsa_parse() 72 dsa->hw_dev_num |= FIELD_PREP(PRESTERA_DSA_DEV_NUM, field); in prestera_dsa_parse() 74 dsa->port_num = (FIELD_GET(PRESTERA_DSA_W0_PORT_NUM, words[0]) << 0) | in prestera_dsa_parse() [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | brcm,bcm7445-switch-v4.0.txt | 12 - #address-cells: must be 1, see dsa/dsa.txt 13 - #size-cells: must be 0, see dsa/dsa.txt 17 - dsa,mii-bus: phandle to the MDIO bus controller, see dsa/dsa.txt 18 - dsa,ethernet: phandle to the CPU network interface controller, see dsa/dsa.txt 19 - #address-cells: must be 2, see dsa/dsa.txt 24 described in dsa/dsa.txt. 106 Example using the old DSA DeviceTree binding:
|
| /kernel/linux/linux-5.10/net/dsa/ |
| D | tag_dsa.c | 3 * net/dsa/tag_dsa.c - (Non-ethertype) DSA tagging 21 * Convert the outermost 802.1q tag to a DSA tag for tagged in dsa_xmit() 22 * packets, or insert a DSA tag between the addresses and in dsa_xmit() 27 * Construct tagged FROM_CPU DSA tag from 802.1q tag. in dsa_xmit() 46 * Construct untagged FROM_CPU DSA tag. in dsa_xmit() 69 * The ethertype field is part of the DSA header. in dsa_rcv() 90 * Convert the DSA header to an 802.1q header if the 'tagged' in dsa_rcv() 91 * bit in the DSA header is set. If the 'tagged' bit is clear, in dsa_rcv() 92 * delete the DSA header entirely. in dsa_rcv() 100 * DSA uses that bit location for another purpose). in dsa_rcv() [all …]
|
| D | tag_edsa.c | 3 * net/dsa/tag_edsa.c - Ethertype DSA tagging 32 * Convert the outermost 802.1q tag to a DSA tag and prepend in edsa_xmit() 33 * a DSA ethertype field is the packet is tagged, or insert in edsa_xmit() 34 * a DSA ethertype plus DSA tag between the addresses and the in edsa_xmit() 43 * Construct tagged FROM_CPU DSA tag from 802.1q tag. in edsa_xmit() 66 * Construct untagged FROM_CPU DSA tag. in edsa_xmit() 137 * If the 'tagged' bit is set, convert the DSA tag to a 802.1q in edsa_rcv() 139 * clear, delete the ethertype and the DSA tag parts. in edsa_rcv() 147 * DSA uses that bit location for another purpose). in edsa_rcv() 155 * Move CFI bit from its place in the DSA header to in edsa_rcv() [all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/marvell/prestera/ |
| D | prestera_dsa.c | 33 int prestera_dsa_parse(struct prestera_dsa *dsa, const u8 *dsa_buf) in prestera_dsa_parse() argument 61 dsa->vlan.is_tagged = FIELD_GET(PRESTERA_DSA_W0_IS_TAGGED, words[0]); in prestera_dsa_parse() 62 dsa->vlan.cfi_bit = FIELD_GET(PRESTERA_DSA_W1_CFI_BIT, words[1]); in prestera_dsa_parse() 63 dsa->vlan.vpt = FIELD_GET(PRESTERA_DSA_W0_VPT, words[0]); in prestera_dsa_parse() 64 dsa->vlan.vid = FIELD_GET(PRESTERA_DSA_W0_VID, words[0]); in prestera_dsa_parse() 65 dsa->vlan.vid &= ~PRESTERA_DSA_VID; in prestera_dsa_parse() 66 dsa->vlan.vid |= FIELD_PREP(PRESTERA_DSA_VID, field); in prestera_dsa_parse() 70 dsa->hw_dev_num = FIELD_GET(PRESTERA_DSA_W0_DEV_NUM, words[0]); in prestera_dsa_parse() 71 dsa->hw_dev_num |= FIELD_PREP(PRESTERA_DSA_DEV_NUM, field); in prestera_dsa_parse() 73 dsa->port_num = (FIELD_GET(PRESTERA_DSA_W0_PORT_NUM, words[0]) << 0) | in prestera_dsa_parse() [all …]
|
| /kernel/linux/linux-6.6/drivers/net/dsa/ |
| D | Kconfig | 5 source "drivers/net/dsa/b53/Kconfig" 20 tristate "DSA mock-up Ethernet switch chip support" 25 exercises the DSA APIs. 27 source "drivers/net/dsa/hirschmann/Kconfig" 78 source "drivers/net/dsa/microchip/Kconfig" 80 source "drivers/net/dsa/mv88e6xxx/Kconfig" 82 source "drivers/net/dsa/ocelot/Kconfig" 84 source "drivers/net/dsa/qca/Kconfig" 86 source "drivers/net/dsa/sja1105/Kconfig" 88 source "drivers/net/dsa/xrs700x/Kconfig" [all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/dsa/ |
| D | dsa-port.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/dsa-port.yaml# 7 title: Generic DSA Switch Port 15 A DSA switch port is a component of a switch that manages one MAC, and can 17 DSA-specific functionality. 34 Should be a list of phandles to other switch's DSA port. This 48 dsa-tag-protocol: 54 - dsa 62 # CPU and DSA ports must have phylink-compatible link descriptions
|
| D | dsa.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/dsa.yaml# 24 dsa,member: 28 A two element list indicates which DSA cluster, and position within the 38 description: A DSA switch without any extra port properties 55 $ref: dsa-port.yaml#
|
| /kernel/linux/linux-6.6/net/dsa/ |
| D | tag.h | 9 #include <net/dsa.h> 88 /* The sad part about attempting to untag from DSA is that we in dsa_untag_bridge_pvid() 93 * from the bridge's data path. This is a configuration that DSA in dsa_untag_bridge_pvid() 106 /* For switches without hardware support for DSA tagging to be able 163 /* Helper for removing DSA header tags from packets in the RX path. 170 * | Destination MAC | Source MAC | DSA header | EType | 189 /* Helper for creating space for DSA header tags in TX path packets. 207 * | Destination MAC | Source MAC | DSA header | EType | 218 /* On RX, eth_type_trans() on the DSA master pulls ETH_HLEN bytes starting from 220 * what the DSA master perceives as the EtherType (the beginning of the L3 [all …]
|
| D | tag_dsa.c | 3 * Regular and Ethertype DSA tagging 6 * Regular DSA 12 * converted to a DSA tag. It expects the same layout when receiving 26 * Pd: | DA | SA | DSA | ET | Payload ... 36 * Ethertype DSA 38 * Uses the exact same tag format as regular DSA, but also includes a 43 * | DA | SA | 0xdada | 0x0000 | DSA | ET | Payload ... 48 #include <linux/dsa/mv88e6xxx.h> 55 #define DSA_NAME "dsa" 61 * enum dsa_cmd - DSA Command [all …]
|
| /kernel/linux/linux-5.10/drivers/net/dsa/ |
| D | Kconfig | 5 source "drivers/net/dsa/b53/Kconfig" 20 tristate "DSA mock-up Ethernet switch chip support" 25 exercises the DSA APIs. 52 source "drivers/net/dsa/microchip/Kconfig" 54 source "drivers/net/dsa/mv88e6xxx/Kconfig" 56 source "drivers/net/dsa/ocelot/Kconfig" 58 source "drivers/net/dsa/qca/Kconfig" 60 source "drivers/net/dsa/sja1105/Kconfig"
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-dsa | 1 What: /sys/bus/event_source/devices/dsa*/format 7 perf_event_attr.config1 for the IDXD DSA pmu. (See also 13 IDXD DSA Spec for possible attribute values):: 24 What: /sys/bus/event_source/devices/dsa*/cpumask 29 IDXD DSA pmu is bound for access to all dsa pmu
|