Searched refs:DSA (Results 1 – 25 of 30) sorted by relevance
12
| /Linux-v5.4/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
68 DSA currently supports 5 different tagging protocols, and a tag-less mode as
[all …]
|
| D | bcm_sf2.rst | 41 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
|
| D | lan9303.rst | 13 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,
|
| 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
78 DSA switches. These switches are capable to tag incoming and outgoing traffic
|
| D | b53.rst | 17 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.
|
| D | sja1105.rst | 145 enslaves eth0 and eth1 (the DSA master of the switch ports). This is because in
173 done by the DSA net devices, which populate the PCP field of the tagging header
175 offloaded flows can be steered to TX queues based on the VLAN PCP, but the DSA
178 sub-interface on the DSA master port, and send normal (0x8100) VLAN-tagged
308 MDIO bus available to Linux within the system (e.g. to the DSA master's MDIO
|
| /Linux-v5.4/net/dsa/ |
| D | Kconfig | 59 tristate "Tag driver for Marvell switches using DSA headers"
62 Marvell switches which use DSA headers.
65 tristate "Tag driver for Marvell switches using EtherType DSA headers"
68 Marvell switches which use EtherType DSA headers.
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/dsa/ |
| D | dsa.txt | 5 probed, they register to the DSA framework, passing a node
16 - dsa,member : A two element list indicates which DSA cluster, and position
35 - link : Should be a list of phandles to other switch's DSA
74 linked into one DSA cluster.
|
| D | lan9303.txt | 21 Note: always use 'reg = <0/1/2>;' for the three DSA ports, even if the device is
|
| D | marvell.txt | 1 Marvell DSA Switch Device Tree Bindings
|
| D | vitesse,vsc73xx.txt | 43 and subnodes of DSA switches.
|
| D | realtek-smi.txt | 61 and subnodes of DSA switches.
|
| D | sja1105.txt | 54 DSA required and optional properties.
|
| D | mt7530.txt | 59 Currently a 2nd CPU port is not supported by DSA code.
|
| /Linux-v5.4/drivers/net/dsa/sja1105/ |
| D | Kconfig | 25 the SJA1105 DSA driver.
33 engine in the SJA1105 DSA driver, which is controlled using a
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-net-dsa | 7 DSA slave network device.
|
| /Linux-v5.4/drivers/net/dsa/ |
| D | Kconfig | 20 tristate "DSA mock-up Ethernet switch chip support"
25 exercises the DSA APIs.
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/ |
| D | hisilicon-hns-dsaf.txt | 1 Hisilicon DSA Fabric device controller
12 - interrupts: should contain the DSA Fabric and rcb interrupt.
|
| D | brcm,bcm7445-switch-v4.0.txt | 93 Example using the old DSA DeviceTree binding:
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | kirkwood-linksys-viper.dts | 227 /* eth1 is connected to the switch at port 6. However DSA only supports a
|
| D | orion5x-netgear-wnr854t.dts | 213 /* Hardwired to DSA switch */
|
| D | kirkwood-dir665.dts | 257 /* eth1 is connected to the switch as well. However DSA only supports a
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/hisilicon/ |
| D | hisilicon.txt | 262 Hisilicon HiP05/HiP06 DSA sub system controller
268 The DSA sub system controller is shared by peripheral controllers in
|
| /Linux-v5.4/drivers/video/fbdev/ |
| D | imsttfb.c | 47 DSA = 3, /* 0x0C */ enumerator
1009 write_reg_le32(par->dc_regs, DSA, dy + dx); in imsttfb_fillrect()
1020 write_reg_le32(par->dc_regs, DSA, dy + dx); in imsttfb_fillrect()
1077 write_reg_le32(par->dc_regs, DSA, fb_offset_new); in imsttfb_copyarea()
|
| /Linux-v5.4/Documentation/scsi/ |
| D | ChangeLog.sym53c8xx_2 | 135 - Allocate separately from the HCB the array for CCBs hashed by DSA.
|
12
