Home
last modified time | relevance | path

Searched full:dsa (Results 1 – 25 of 45) sorted by relevance

12

/Documentation/ABI/stable/
Dsysfs-driver-dma-idxd1 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 …]
/Documentation/devicetree/bindings/net/
Dbrcm,bcm7445-switch-v4.0.txt3 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:
Dhisilicon-hns-dsaf.txt1 Hisilicon DSA Fabric device controller
7 - mode: dsa fabric mode string. only support one of dsaf modes like these:
12 - interrupts: should contain the DSA Fabric and rcb interrupt.
21 The fourth region is dsa fabric base register and size. It is not required for
58 dsaf0: dsa@c7000000 {
/Documentation/networking/dsa/
Dconfiguration.rst4 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 …]
Ddsa.rst5 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 …]
Dbcm_sf2.rst41 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
Dlan9303.rst13 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,
Db53.rst16 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`
Dindex.rst8 dsa
/Documentation/ABI/testing/
Dsysfs-bus-event_source-devices-dsa1 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
Dsysfs-class-net-dsa1 What: /sys/class/net/<iface>/dsa/tagging
7 tagging protocol used by the DSA network devices that are
10 attached DSA switches, if this operation is supported by the
11 driver. Changing the tagging protocol must be done with the DSA
/Documentation/devicetree/bindings/net/dsa/
Ddsa-port.yaml4 $id: http://devicetree.org/schemas/net/dsa/dsa-port.yaml#
32 Should be a list of phandles to other switch's DSA port. This
46 dsa-tag-protocol:
52 - dsa
79 # CPU and DSA ports must have phylink-compatible link descriptions
Ddsa.yaml4 $id: http://devicetree.org/schemas/net/dsa/dsa.yaml#
25 dsa,member:
29 A two element list indicates which DSA cluster, and position within the
49 $ref: dsa-port.yaml#
Ddsa.txt4 See Documentation/devicetree/bindings/net/dsa/dsa.yaml for the documentation.
Dmicrochip,ksz.yaml4 $id: http://devicetree.org/schemas/net/dsa/microchip,ksz.yaml#
14 - $ref: dsa.yaml#
18 # See Documentation/devicetree/bindings/net/dsa/dsa.yaml for a list of additional
Dhirschmann,hellcreek.yaml4 $id: http://devicetree.org/schemas/net/dsa/hirschmann,hellcreek.yaml#
10 - $ref: dsa.yaml#
86 dsa,member = <0 0>;
Dlan9303.txt19 described in dsa/dsa.txt. The CPU port of this switch is always port 0.
21 Note: always use 'reg = <0/1/2>;' for the three DSA ports, even if the device is
Dvitesse,vsc73xx.txt42 See net/dsa/dsa.txt for a list of additional required and optional properties
43 and subnodes of DSA switches.
Darrow,xrs700x.yaml4 $id: http://devicetree.org/schemas/net/dsa/arrow,xrs700x.yaml#
10 - $ref: dsa.yaml#
Dmarvell.txt1 Marvell DSA Switch Device Tree Bindings
8 If you need a stable binding, use the old dsa.txt binding.
14 Additional required and optional properties can be found in dsa.txt.
Drenesas,rzn1-a5psw.yaml4 $id: http://devicetree.org/schemas/net/dsa/renesas,rzn1-a5psw.yaml#
17 - $ref: dsa.yaml#
110 dsa,member = <0 0>;
Dmediatek,mt7530.yaml4 $id: http://devicetree.org/schemas/net/dsa/mediatek,mt7530.yaml#
23 using MDIO. The DSA driver currently doesn't support this.
45 - Port 5 can be wired to an external phy. Port 5 becomes a DSA slave.
70 - Port 5 can be muxed to an external phy. Port 5 becomes a DSA slave.
171 - $ref: dsa-port.yaml#
186 mt7530-dsa-port:
212 mt7531-dsa-port:
241 - $ref: dsa.yaml#
261 $ref: "#/$defs/mt7530-dsa-port"
271 $ref: "#/$defs/mt7531-dsa-port"
[all …]
Dlantiq-gswip.txt16 See Documentation/devicetree/bindings/net/dsa/dsa.txt for a list of
56 dsa,member = <0 0>;
Dbrcm,sf2.yaml4 $id: http://devicetree.org/schemas/net/dsa/brcm,sf2.yaml#
101 - $ref: "dsa.yaml#"
/Documentation/networking/
Dtimestamping.rst604 3.2.1 DSA (Distributed Switch Architecture) switches
609 a port multiplier with optional forwarding acceleration features. Each DSA
614 When a DSA switch is attached to a host port, PTP synchronization has to
616 jitter between the host port and its PTP partner. For this reason, some DSA
619 measure wire and PHY propagation latencies. Timestamping DSA switches are
621 for the fact that the DSA interfaces are in fact virtual in terms of network
623 interfaces of a DSA switch to share the same PHC.
625 By design, PTP timestamping with a DSA switch does not need any special
627 host port also supports PTP timestamping, DSA will take care of intercepting
631 anybody else except for the DSA switch port must be prevented from doing so.
[all …]

12