Home
last modified time | relevance | path

Searched refs:DSA (Results 1 – 25 of 36) sorted by relevance

12

/Linux-v6.1/Documentation/networking/dsa/
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
68 DSA supports many vendor-specific tagging protocols, one software-defined
[all …]
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 …]
Dbcm_sf2.rst41 The driver is located in ``drivers/net/dsa/bcm_sf2.c`` and is implemented as a DSA
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``.
21 interfaces (which is the default state of a DSA device). Due to HW limitations,
Db53.rst17 DSA driver; see ``Documentation/networking/dsa/dsa.rst`` for details on the
36 DSA driver and will work like all DSA drivers which supports tagging.
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-class-net-dsa7 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
Dsysfs-bus-event_source-devices-dsa7 perf_event_attr.config1 for the IDXD DSA pmu. (See also
13 IDXD DSA Spec for possible attribute values)::
29 IDXD DSA pmu is bound for access to all dsa pmu
/Linux-v6.1/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 …]
/Linux-v6.1/drivers/net/dsa/sja1105/
DKconfig32 the SJA1105 DSA driver.
41 engine in the SJA1105 DSA driver, which is controlled using a
/Linux-v6.1/net/dsa/
DKconfig70 tristate "Tag driver for Marvell switches using DSA headers"
74 Marvell switches which use DSA headers.
77 tristate "Tag driver for Marvell switches using EtherType DSA headers"
81 Marvell switches which use EtherType DSA headers.
/Linux-v6.1/Documentation/ABI/stable/
Dsysfs-driver-dma-idxd49 The read buffers represent resources within the DSA
51 support operations. See DSA spec v1.2 9.2.4 Total Read Buffers.
124 device. See DSA spec v1.2 9.2.8 GENCFG on Global Read Buffer Limit.
251 Description: Enable the use of global read buffer limit for the group. See DSA
259 by all engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read
267 engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read Buffers
/Linux-v6.1/drivers/net/dsa/
DKconfig20 tristate "DSA mock-up Ethernet switch chip support"
24 exercises the DSA APIs.
/Linux-v6.1/Documentation/devicetree/bindings/net/
Dbrcm,bcm7445-switch-v4.0.txt11 Example using the old DSA DeviceTree binding:
Dhisilicon-hns-dsaf.txt1 Hisilicon DSA Fabric device controller
12 - interrupts: should contain the DSA Fabric and rcb interrupt.
/Linux-v6.1/drivers/net/ethernet/mscc/
DKconfig23 used by switchdev as well as by DSA drivers.
/Linux-v6.1/Documentation/devicetree/bindings/net/dsa/
Dlan9303.txt21 Note: always use 'reg = <0/1/2>;' for the three DSA ports, even if the device is
Dmarvell.txt1 Marvell DSA Switch Device Tree Bindings
Dvitesse,vsc73xx.txt43 and subnodes of DSA switches.
/Linux-v6.1/arch/arm/boot/dts/
Daspeed-bmc-facebook-elbert.dts192 * BCM53134 is added to "bcm53xx" DSA driver.
Dintel-ixp42x-ixdpg425.dts93 * of Realtek DSA switch on the board.
Dkirkwood-linksys-viper.dts227 /* eth1 is connected to the switch at port 6. However DSA only supports a
Dorion5x-netgear-wnr854t.dts208 /* Hardwired to DSA switch */
Dkirkwood-dir665.dts257 /* eth1 is connected to the switch as well. However DSA only supports a
/Linux-v6.1/Documentation/networking/devlink/
Ddevlink-port.rst28 - This indicates a DSA interconnect port.
30 - This indicates a CPU port applicable only to DSA.
/Linux-v6.1/drivers/video/fbdev/
Dimsttfb.c48 DSA = 3, /* 0x0C */ enumerator
1010 write_reg_le32(par->dc_regs, DSA, dy + dx); in imsttfb_fillrect()
1021 write_reg_le32(par->dc_regs, DSA, dy + dx); in imsttfb_fillrect()
1078 write_reg_le32(par->dc_regs, DSA, fb_offset_new); in imsttfb_copyarea()

12