Home
last modified time | relevance | path

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

12

/linux/Documentation/networking/dsa/
H A 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 "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
65 NB: for the past 15 years, the DSA subsystem had been making use of the terms
[all …]
H A 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 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 …]
H A 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 user MDIO bus
74 "double" programming. Using DSA, and setting ``ds->phys_mii_mask`` accordingly, we
H A 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,
H A 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.
H A Dsja1105.rst120 done by the DSA net devices, which populate the PCP field of the tagging header
122 offloaded flows can be steered to TX queues based on the VLAN PCP, but the DSA
125 sub-interface on the DSA conduit port, and send normal (0x8100) VLAN-tagged
392 MDIO bus available to Linux within the system (e.g. to the DSA conduit's MDIO
/linux/Documentation/ABI/testing/
H A 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
H A 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/drivers/net/dsa/sja1105/
H A DKconfig32 the SJA1105 DSA driver.
41 engine in the SJA1105 DSA driver, which is controlled using a
/linux/net/dsa/
H A DKconfig76 tristate "Tag driver for Marvell switches using DSA headers"
80 Marvell switches which use DSA headers.
83 tristate "Tag driver for Marvell switches using EtherType DSA headers"
87 Marvell switches which use EtherType DSA headers.
/linux/Documentation/devicetree/bindings/net/
H A Dhisilicon-hns-dsaf.txt1 Hisilicon DSA Fabric device controller
12 - interrupts: should contain the DSA Fabric and rcb interrupt.
H A Dbrcm,bcm7445-switch-v4.0.txt11 Example using the old DSA DeviceTree binding:
/linux/drivers/net/dsa/
H A DKconfig20 tristate "DSA mock-up Ethernet switch chip support"
25 exercises the DSA APIs.
/linux/drivers/net/ethernet/mscc/
H A DKconfig24 used by switchdev as well as by DSA drivers.
/linux/Documentation/devicetree/bindings/net/dsa/
H A Dlan9303.txt21 Note: always use 'reg = <0/1/2>;' for the three DSA ports, even if the device is
/linux/arch/arm/boot/dts/aspeed/
H A Daspeed-bmc-facebook-elbert.dts192 * BCM53134 is added to "bcm53xx" DSA driver.
/linux/arch/arm/boot/dts/intel/ixp/
H A Dintel-ixp42x-ixdpg425.dts93 * of Realtek DSA switch on the board.
H A Dintel-ixp42x-usrobotics-usr8200.dts239 /* EthC LAN connected to the Marvell DSA Switch */
/linux/arch/arm64/boot/dts/marvell/
H A Darmada-3720-espressobin.dtsi16 /* for DSA user port device */
/linux/arch/arm/boot/dts/marvell/
H A Dkirkwood-linksys-viper.dts226 /* eth1 is connected to the switch at port 6. However DSA only supports a
H A Dorion5x-netgear-wnr854t.dts212 /* Hardwired to DSA switch */
H A Dkirkwood-dir665.dts256 /* eth1 is connected to the switch as well. However DSA only supports a
/linux/drivers/video/fbdev/
H A 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()
/linux/Documentation/scsi/
H A DChangeLog.sym53c8xx_2135 - Allocate separately from the HCB the array for CCBs hashed by DSA.
/linux/Documentation/arch/x86/
H A Dsva.rst73 For example, the Intel Data Streaming Accelerator (DSA) uses
285 DSA spec:

12