Home
last modified time | relevance | path

Searched refs:dsa (Results 1 – 25 of 51) sorted by relevance

123

/Linux-v4.19/scripts/coccinelle/api/debugfs/
Ddebugfs_simple_attr.cocci18 @dsa@
28 identifier dsa.dsa_fops;
35 identifier dsa.dsa_fops;
36 expression dsa.dsa_get, dsa.dsa_set, dsa.dsa_fmt;
43 identifier dsa.dsa_fops;
49 identifier dsa.dsa_fops;
50 expression dsa.dsa_get, dsa.dsa_set, dsa.dsa_fmt;
57 fops << dsa.dsa_fops;
58 p << dsa.p;
64 fops << dsa.dsa_fops;
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/net/
Dbrcm,bcm7445-switch-v4.0.txt12 - #address-cells: must be 1, see dsa/dsa.txt
13 - #size-cells: must be 0, see dsa/dsa.txt
17 - dsa,mii-bus: phandle to the MDIO bus controller, see dsa/dsa.txt
18 - dsa,ethernet: phandle to the CPU network interface controller, see dsa/dsa.txt
19 - #address-cells: must be 2, see dsa/dsa.txt
24 described in dsa/dsa.txt.
Dhisilicon-hns-dsaf.txt7 - mode: dsa fabric mode string. only support one of dsaf modes like these:
21 The fourth region is dsa fabric base register and size. It is not required for
58 dsaf0: dsa@c7000000 {
/Linux-v4.19/drivers/scsi/sym53c8xx_2/
Dsym_fw1.h285 RADDR_1 (dsa),
288 RADDR_1 (dsa),
345 RADDR_1 (dsa),
685 RADDR_1 (dsa),
731 RADDR_1 (dsa),
837 RADDR_1 (dsa),
874 SCR_LOAD_REG (dsa, 0xff),
912 RADDR_1 (dsa),
913 SCR_SFBR_REG (dsa, SCR_SHL, 0),
915 SCR_REG_REG (dsa, SCR_SHL, 0),
[all …]
Dsym_fw2.h257 SCR_LOAD_ABS (dsa, 4),
264 SCR_LOAD_REL (dsa, 4),
704 SCR_STORE_ABS (dsa, 4),
706 SCR_LOAD_ABS (dsa, 4),
837 SCR_LOAD_REG (dsa, 0xff),
872 SCR_LOAD_ABS (dsa, 4),
874 SCR_SFBR_REG (dsa, SCR_SHL, 0),
876 SCR_REG_REG (dsa, SCR_SHL, 0),
878 SCR_REG_REG (dsa, SCR_AND, 0x3c),
880 SCR_LOAD_REL (dsa, 4),
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/net/dsa/
Ddsa.txt22 - dsa,member : A two element list indicates which DSA cluster, and position
87 dsa,member = <0 0>;
138 dsa,member = <0 1>;
205 dsa,member = <0 2>;
269 - compatible : Should be "marvell,dsa"
274 - dsa,ethernet : Should be a phandle to a valid Ethernet device node
275 - dsa,mii-bus : Should be a phandle to a valid MDIO bus device node
304 labels are "cpu" to indicate a CPU port and "dsa" to
307 Note that a port labelled "dsa" will imply checking for the uplink phandle
328 global dsa,mii-bus defined above, for this switch.
[all …]
Dksz.txt11 See Documentation/devicetree/bindings/net/dsa/dsa.txt for a list of additional
Dlan9303.txt19 described in dsa/dsa.txt. The CPU port of this switch is always port 0.
Drealtek-smi.txt60 See net/dsa/dsa.txt for a list of additional required and optional properties
123 compatible = "realtek,smi-mdio", "dsa-mdio";
Dqca8k.txt15 described in dsa/dsa.txt. As the QCA8K switches do not have a N:N mapping of
Dvitesse,vsc73xx.txt36 See net/dsa/dsa.txt for a list of additional required and optional properties
Dmt7530.txt34 See Documentation/devicetree/bindings/net/dsa/dsa.txt for a list of additional
Db53.txt49 See Documentation/devicetree/bindings/net/dsa/dsa.txt for a list of additional
/Linux-v4.19/arch/arm/boot/dts/
Dkirkwood-rd88f6281.dtsi53 dsa {
56 compatible = "marvell,dsa";
60 dsa,ethernet = <&eth0port>;
61 dsa,mii-bus = <&mdio>;
Dkirkwood-mv88f6281gtw-ge.dts111 dsa {
114 compatible = "marvell,dsa";
118 dsa,ethernet = <&eth0port>;
119 dsa,mii-bus = <&mdio>;
Darmada-388-clearfog.dts33 dsa@0 {
36 compatible = "marvell,dsa";
37 dsa,ethernet = <&eth1>;
38 dsa,mii-bus = <&mdio>;
Dvf610-zii-dev-rev-b.dts74 dsa,member = <0 0>;
105 label = "dsa";
158 dsa,member = <0 1>;
189 label = "dsa";
201 label = "dsa";
243 dsa,member = <0 2>;
293 label = "dsa";
Dkirkwood-linksys-viper.dts70 dsa {
73 compatible = "marvell,dsa";
77 dsa,ethernet = <&eth0port>;
78 dsa,mii-bus = <&mdio>;
Darmada-370-rd.dts118 dsa {
121 compatible = "marvell,dsa";
125 dsa,ethernet = <&eth1>;
126 dsa,mii-bus = <&mdio>;
Dkirkwood-dir665.dts194 dsa {
197 compatible = "marvell,dsa";
201 dsa,ethernet = <&eth0port>;
202 dsa,mii-bus = <&mdio>;
Darmada-xp-linksys-mamba.dts214 dsa {
217 compatible = "marvell,dsa";
221 dsa,ethernet = <&eth0>;
222 dsa,mii-bus = <&mdio>;
/Linux-v4.19/Documentation/networking/dsa/
Dlan9303.txt13 Documentation/networking/dsa/dsa.txt.
15 See Documentation/devicetree/bindings/net/dsa/lan9303.txt for device tree
Dbcm_sf2.txt40 The driver is located in drivers/net/dsa/bcm_sf2.c and is implemented as a DSA
41 driver; see Documentation/networking/dsa/dsa.txt for details on the subsystem
48 net/dsa/tag_brcm.c.
57 provided in net/dsa/dsa.c. The reason for that is because the DSA subsystem gets
Ddsa.txt35 ports are referred to as "dsa" ports in DSA terminology and code. A collection
57 "dsa" ports because:
63 - the "dsa" port(s) are just conduits between two or more switches, and as such
73 net/dsa/tag_trailer.c: Marvell's 4 trailer tag mode (legacy)
74 net/dsa/tag_dsa.c: Marvell's original DSA tag
75 net/dsa/tag_edsa.c: Marvell's enhanced DSA tag
76 net/dsa/tag_brcm.c: Broadcom's 4 bytes tag
77 net/dsa/tag_qca.c: Qualcomm's 2 bytes tag
127 net/dsa/dsa.c:
130 net/dsa/tag_*.c
[all …]
/Linux-v4.19/drivers/net/dsa/
DKconfig4 source "drivers/net/dsa/b53/Kconfig"
42 source "drivers/net/dsa/microchip/Kconfig"
44 source "drivers/net/dsa/mv88e6xxx/Kconfig"

123