Searched full:dsa (Results 1 – 25 of 50) sorted by relevance
12
| /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 …]
|
| /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:
|
| D | hisilicon-hns-dsaf.txt | 1 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/ |
| 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 user interface is brought up, the conduit interface is 44 - when the conduit interface is brought down, all DSA user 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 | 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 "conduit" 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 | 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 user MDIO bus 74 "double" programming. Using DSA, and setting ``ds->phys_mii_mask`` accordingly, we
|
| 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,
|
| 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`
|
| /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 46 $ref: dsa-port.yaml#
|
| D | marvell,mv88e6060.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/marvell,mv88e6060.yaml# 7 title: Marvell MV88E6060 DSA switch 18 from many other DSA switches this switch does not have an internal 25 The MV88E6060 is the oldest Marvell DSA switch product, and 37 - $ref: dsa.yaml#/$defs/ethernet-ports
|
| D | dsa.txt | 4 See Documentation/devicetree/bindings/net/dsa/dsa.yaml for the documentation.
|
| D | hirschmann,hellcreek.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/hirschmann,hellcreek.yaml# 10 - $ref: dsa.yaml#/$defs/ethernet-ports 86 dsa,member = <0 0>;
|
| D | lan9303.txt | 19 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
|
| D | microchip,ksz.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/microchip,ksz.yaml# 17 # See Documentation/devicetree/bindings/net/dsa/dsa.yaml for a list of additional 96 $ref: dsa.yaml#/$defs/ethernet-ports 102 $ref: dsa-port.yaml#
|
| D | vitesse,vsc73xx.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/vitesse,vsc73xx.yaml# 7 title: Vitesse VSC73xx DSA Switches 13 The Vitesse DSA Switches were produced in the early-to-mid 2000s. 53 - $ref: dsa.yaml#/$defs/ethernet-ports
|
| D | arrow,xrs700x.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/arrow,xrs700x.yaml# 10 - $ref: dsa.yaml#/$defs/ethernet-ports
|
| D | brcm,sf2.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/brcm,sf2.yaml# 85 $ref: dsa-port.yaml# 99 - $ref: dsa.yaml#
|
| D | renesas,rzn1-a5psw.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/renesas,rzn1-a5psw.yaml# 17 - $ref: dsa.yaml#/$defs/ethernet-ports 104 dsa,member = <0 0>;
|
| D | mediatek,mt7530.yaml | 4 $id: http://devicetree.org/schemas/net/dsa/mediatek,mt7530.yaml# 30 using MDIO. The DSA driver currently doesn't support MT7620 variants. 63 - Port 5 can be wired to an external phy. Port 5 becomes a DSA user port. 189 mt7530-dsa-port: 215 mt7531-dsa-port: 244 - $ref: dsa.yaml#/$defs/ethernet-ports 264 $ref: "#/$defs/mt7530-dsa-port" 274 $ref: "#/$defs/mt7531-dsa-port" 284 $ref: "#/$defs/mt7530-dsa-port" 295 $ref: "#/$defs/mt7530-dsa-port"
|
| /Documentation/devicetree/bindings/iio/frequency/ |
| D | adi,admfm2000.yaml | 16 It consists of a LNA, mixer, IF filter, DSA, and IF amplifier for each down 67 DSA-V4 DSA-V3 DSA-V2 DSA-V1 DSA-V0 77 - description: DSA-V0 GPIO 78 - description: DSA-V1 GPIO 79 - description: DSA-V2 GPIO 80 - description: DSA-V3 GPIO 81 - description: DSA-V4 GPIO
|
| /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
|
| D | sysfs-class-net-dsa | 1 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/driver-api/crypto/iaa/ |
| D | iaa-crypto.rst | 226 /sys/bus/dsa/drivers/crypto/ 240 echo 0 > /sys/bus/dsa/drivers/crypto/verify_compress 272 echo async_irq > /sys/bus/dsa/drivers/crypto/sync_mode 277 echo async > /sys/bus/dsa/drivers/crypto/sync_mode 282 echo sync > /sys/bus/dsa/drivers/crypto/sync_mode 289 '/sys/bus/dsa/drivers/crypto/sync_mode' will internally enable the 463 # cat /sys/bus/dsa/devices/iax1/state 465 # cat /sys/bus/dsa/devices/iax1/wq1.0/state 801 The 'IAA config path' is /sys/bus/dsa/devices and contains 805 odd-numbered devices; the even-numbered devices are DSA devices and [all …]
|
| /Documentation/networking/ |
| D | timestamping.rst | 653 3.2.1 DSA (Distributed Switch Architecture) switches 658 a port multiplier with optional forwarding acceleration features. Each DSA 663 When a DSA switch is attached to a host port, PTP synchronization has to 665 jitter between the host port and its PTP partner. For this reason, some DSA 668 measure wire and PHY propagation latencies. Timestamping DSA switches are 670 for the fact that the DSA interfaces are in fact virtual in terms of network 672 interfaces of a DSA switch to share the same PHC. 674 By design, PTP timestamping with a DSA switch does not need any special 676 host port also supports PTP timestamping, DSA will take care of intercepting 680 anybody else except for the DSA switch port must be prevented from doing so. [all …]
|
12