Home
last modified time | relevance | path

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

12

/linux/Documentation/networking/dsa/
A Ddsa.rst39 interfaces in DSA terminology and code.
130 CPU port can be configured to use either the DSA or the Ethertype DSA (EDSA)
142 no DSA links in this fabric, and each switch constitutes a disjoint DSA switch
143 tree. The DSA links are viewed as simply a pair of a DSA master (the out-facing
145 downstream DSA switch).
162 for the DSA master.
187 Packet Steering) on the DSA master would be broken. The DSA framework deals
373 Lack of CPU/DSA network devices
376 DSA does not currently create slave network devices for the CPU or DSA ports, as
388 Common pitfalls using DSA setups
[all …]
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 slave interface is brought up, the master interface is
44 - when the master interface is brought down, all DSA slave interfaces are
320 explicit) are treated by DSA as ``static`` even if they are ``local``.
326 # behaves the same for DSA as this command:
335 such, will not forward it, as opposed to DSA.
346 Since kernel v5.14, DSA has gained stronger integration with the bridge's
[all …]
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 slave MDIO bus
74 "double" programming. Using DSA, and setting ``ds->phys_mii_mask`` accordingly, we
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,
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.
/linux/Documentation/ABI/testing/
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
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/Documentation/devicetree/bindings/net/dsa/
A Docelot.txt36 operate as an entire slave DSA chip. NPI functionality (and therefore DSA
42 well, regardless of whether it is configured as the DSA master or not. This is
55 For the rest of the device tree binding definitions, which are standard DSA and
A Ddsa.yaml29 A two element list indicates which DSA cluster, and position within the
64 Should be a list of phandles to other switch's DSA port. This
A Dlan9303.txt21 Note: always use 'reg = <0/1/2>;' for the three DSA ports, even if the device is
A Dmarvell.txt1 Marvell DSA Switch Device Tree Bindings
A Dvitesse,vsc73xx.txt43 and subnodes of DSA switches.
/linux/Documentation/networking/
A 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
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
633 In the generic layer, DSA provides the following infrastructure for PTP
661 - ``.port_rxtstamp()``: On RX, the BPF classifier is run by DSA to
667 DSA header, or attached in other ways to the packet), or out-of-band
[all …]
/linux/net/dsa/
A 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/drivers/net/dsa/sja1105/
A DKconfig32 the SJA1105 DSA driver.
41 engine in the SJA1105 DSA driver, which is controlled using a
/linux/drivers/net/dsa/
A DKconfig20 tristate "DSA mock-up Ethernet switch chip support"
24 exercises the DSA APIs.
/linux/Documentation/devicetree/bindings/net/
A Dhisilicon-hns-dsaf.txt1 Hisilicon DSA Fabric device controller
12 - interrupts: should contain the DSA Fabric and rcb interrupt.
A Dbrcm,bcm7445-switch-v4.0.txt11 Example using the old DSA DeviceTree binding:
/linux/drivers/net/ethernet/mscc/
A DKconfig23 used by switchdev as well as by DSA drivers.
/linux/arch/arm/boot/dts/
A Dintel-ixp42x-ixdpg425.dts93 * of Realtek DSA switch on the board.
A Dkirkwood-linksys-viper.dts227 /* eth1 is connected to the switch at port 6. However DSA only supports a
A Dorion5x-netgear-wnr854t.dts213 /* Hardwired to DSA switch */
A Dkirkwood-dir665.dts257 /* eth1 is connected to the switch as well. However DSA only supports a
/linux/Documentation/networking/devlink/
A Ddevlink-port.rst28 - This indicates a DSA interconnect port.
30 - This indicates a CPU port applicable only to DSA.
/linux/drivers/video/fbdev/
A Dimsttfb.c47 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()

Completed in 33 milliseconds

12