};
enetc_port3: pci@0,6 {
reg = <0x000600 0 0 0 0>;
fixed-link {
speed = <1000>;
full-duplex;
};
};
4.2.12.3.3 Linux usage
4.2.12.3.3.1 Driver probing
A successful driver probe will produce the following output in the boot log:
[1.074990] mscc_felix 0000:00:00.5: Felix Switch Driver - version 0.3 probed
If the driver is successfully probed, each switch port defined in the device tree will have its own network device interface. After
udev applies the networking rules, the switch network interfaces are renamed to swpX, where X represents the port number.
If CPU port function is enabled on any switch port, the network device connected to it must be ready or else the
driver probing will fail.
NOTE
4.2.12.3.3.2 Connecting to the host CPU
On the LS1028A SoC, the L2Switch is connected to the host CPU via two SoC internal MAC-to-MAC port connections between
the switch and corresponding ENETC Ethernet endpoints:
• ENETC PF2 (or ENETC Port 2) and switch port #4
• ENETC PF6 (or ENETC Port 3) and switch port #5
Besides these MAC-to-MAC connections with the host CPU, the L2Switch IP allows for a single switch port to work in CPU port
mode.
The following table summarizes the differences between CPU and non-CPU port modes:
Feature CPU port Non-CPU port
Allows frame injection/extraction Yes No
Tags frames with custom header Yes No
Destination for control frames,for example, STP Yes No
PTP offload Yes No
Flow control No Yes
Requires peer net device as proxy
1
No Yes
1. In non-CPU mode the user needs to use the peer network interface to send and receive packets instead of the actual switch
port interface. In CPU port mode, the user will use the net device interface of the switch port or the bridge interface.
The below figure shows the connection of the L2Switch with the host CPU:
Device Drivers
Layerscape LS1028A BSP User Guide, Rev. 0.3, 04/2019
NXP Semiconductors
97
To Next Page
Loading...
