1 Microchip Ocelot switch driver family
2 =====================================
7 Currently the switches supported by the felix driver are:
12 The VSC9959 switch is found in the NXP LS1028A. It is a PCI device, part of the
13 larger ENETC root complex. As a result, the ethernet-switch node is a sub-node
14 of the PCIe root complex node and its "reg" property conforms to the parent
17 * reg: Specifies PCIe Device Number and Function Number of the endpoint device,
18 in this case for the Ethernet L2Switch it is PF5 (of device 0, bus 0).
20 It does not require a "compatible" string.
22 The interrupt line is used to signal availability of PTP TX timestamps and for
25 For the external switch ports, depending on board configuration, "phy-mode" and
26 "phy-handle" are populated by board specific device tree instances. Ports 4 and
27 5 are fixed as internal ports in the NXP LS1028A instantiation.
29 The CPU port property ("ethernet") configures the feature called "NPI port" in
30 the Ocelot hardware core. The CPU port in Ocelot is a set of queues, which are
31 connected, in the Node Processor Interface (NPI) mode, to an Ethernet port.
32 By default, in fsl-ls1028a.dtsi, the NPI port is assigned to the internal
33 2.5Gbps port@4, but can be moved to the 1Gbps port@5, depending on the specific
34 use case. Moving the NPI port to an external switch port is hardware possible,
35 but there is no platform support for the Linux system on the LS1028A chip to
36 operate as an entire slave DSA chip. NPI functionality (and therefore DSA
37 tagging) is supported on a single port at a time.
39 Any port can be disabled (and in fsl-ls1028a.dtsi, they are indeed all disabled
40 by default, and should be enabled on a per-board basis). But if any external
41 switch port is enabled at all, the ENETC PF2 (enetc_port2) should be enabled as
42 well, regardless of whether it is configured as the DSA master or not. This is
43 because the Felix PHYLINK implementation accesses the MAC PCS registers, which
44 in hardware truly belong to the ENETC port #2 and not to Felix.
46 Supported PHY interface types (appropriate SerDes protocol setting changes are
47 needed in the RCW binary):
49 * phy_mode = "internal": on ports 4 and 5
50 * phy_mode = "sgmii": on ports 0, 1, 2, 3
51 * phy_mode = "qsgmii": on ports 0, 1, 2, 3
52 * phy_mode = "usxgmii": on ports 0, 1, 2, 3
53 * phy_mode = "2500base-x": on ports 0, 1, 2, 3
55 For the rest of the device tree binding definitions, which are standard DSA and
56 PCI, refer to the following documents:
58 Documentation/devicetree/bindings/net/dsa/dsa.txt
59 Documentation/devicetree/bindings/pci/pci.txt
64 pcie@1f0000000 { /* Integrated Endpoint Root Complex */
66 reg = <0x000500 0 0 0 0>;
68 interrupts = <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>;
95 /* Tagging CPU port */
98 ethernet = <&enetc_port2>;
99 phy-mode = "internal";
107 /* Non-tagging CPU port */
110 phy-mode = "internal";
123 The VSC9953 switch is found inside NXP T1040. It is a platform device with the
124 following required properties:
127 Must be "mscc,vsc9953-switch".
129 Supported PHY interface types (appropriate SerDes protocol setting changes are
130 needed in the RCW binary):
132 * phy_mode = "internal": on ports 8 and 9
133 * phy_mode = "sgmii": on ports 0, 1, 2, 3, 4, 5, 6, 7
134 * phy_mode = "qsgmii": on ports 0, 1, 2, 3, 4, 5, 6, 7
139 ethernet-switch@800000 {
140 #address-cells = <0x1>;
142 compatible = "mscc,vsc9953-switch";
144 reg = <0x800000 0x290000>;
147 #address-cells = <0x1>;
192 phy-mode = "internal";
203 phy-mode = "internal";