Introduction
Enet LLD is an unified Ethernet driver that support Ethernet peripherals found in TI SoCs, such as CPSW and ICSSG. Please refer to the SDK release notes to find out what peripherals are currently supported.
The diagram below shows the overall software architecture of the Enet low-level driver. A top-level driver layer provides the interface that the applications can use to configure the switch and to send/receive Ethernet frames.
For instance, the CPSW support in the Enet driver consists of several software submodules that mirror those of the CPSW hardware, like DMA, ALE, MAC port, host port, MDIO, etc. Additionally, the Enet driver also includes PHY driver support as well as a resource manager to administrate the CPSW resources.
Enet LLD relies on other drivers like UDMA for data transfer to/from the Ethernet peripheral's host port to the other processing cores inside the TI SoC devices. For the lower level access to the hardware registers, Enet LLD relies on the Chip Support Library (CSL).
Back To Top
Getting Familiar with Enet LLD APIs
The Enet LLD APIs can be broadly divided into two categories: control and data path. The control APIs can be used to configure all Ethernet hardware submodules like FDB, MAC port, host port, MDIO, statistics, as well as PHY drivers and resource management. The data path APIs are exclusive for the DMA-based data transfers between the TI SoC processing cores and the Ethernet peripheral.
The main APIs of the Enet LLD are the following:
It's worth noting that the control path APIs are mainly IOCTL-based, and the data path APIs are direct functions in order to avoid any additional overhead associated with IOCTL calls as DMA data operations occur highly frequently.
IOCTL Interface
IOCTLs are system calls that take an argument specifying the command code and can take none or additional parameters via Enet_IoctlPrms argument. IOCTL are used by all Enet submodules except for DMA.
The Enet_IoctlPrms parameter structure consists of input and output argument pointers and their corresponding size. The following helper macros are provided to help construct the IOCTL params:
where prms in a pointer to Enet_IoctlPrms variable, in is the pointer to IOCTL input argument and out is the pointer to IOCTL output argument.
It's recommended that the application doesn't set the Enet_IoctlPrms members individually, but only through the helper macros listed above.
Please refer to the individual IOCTL command to find out if it requires input and/or output parameters.
Back To Top
Integrating Enet LLD into User's Application
Developers who wish to add network connectivity to the applications running on TI SoCs, will have to integrate Enet LLD by following the below sequence:
- Init Sequence. One-time initialization before using any Enet LLD APIs.
- Peripheral Open Sequence. Opens an Ethernet peripheral, it's called for each peripheral that the application intends to use, i.e. ICSSG0 and CPSW.
- Port Open Sequence. Opens a MAC port. For peripherals that provide multiple MAC port (i.e. CPSW9G that has 8 MAC ports), this sequence must be followed for each MAC port. This section also covers MAC-PHY and MAC-MAC links.
- Packet Send/Receive Sequence. DMA TX and RX channel open sequences as well as functions to use to submit and retrieve queue of packets to/from the driver.
- Port Close Sequence. Closes a MAC port. Application has to close all MAC ports which were opened in step 3 when no longer needs those ports.
- Peripheral Close Sequence. Closes an Ethernet peripheral when the application no longer needs it. This sequence must be followed for each peripheral that was opened in step 2.
- Deinit Sequence. One-time deinitialization once application is done using Enet LLD.
Each of these sequences will be covered in detail in the following sections.
Init Sequence
This is a one-time initialization where the application sets the OSAL and utils functions that Enet LLD will use throughout its lifecycle.
At this stage Enet LLD also initializes its SoC layer which contains data about the Ethernet hardware available in the TI device.
The application should follow the next steps:
- (Optional) Enet_initOsalCfg() to initialize the OSAL configuration (see EnetOsal_Cfg) with a default implementation. The default implementation of Enet OSAL interface is based on OSAL layer. Typically, applications can directly use the default Enet OSAL implementation, unless Enet is being used on another OS (i.e. QNX) of if OS is not supported by OSAL layer.
- (Optional) Enet_initUtilsCfg() to initialize utils configuration (see EnetUtils_Cfg) with a default implementation. The default implementation of Enet Utils interface is UART-based logging and one-to-one address translations (physical-to-virtual and virtual-to-physical). Applications may want to pass their own utils' print function if UART is not available. Similarly, if a MMU is present and used, applications may need to pass their own address translation functions corresponding to the MMU configuration.
utilsCfg.print = UART_printf;
utilsCfg.physToVirt = &myPhysToVirtFxn;
utilsCfg.virtToPhys = &myVirtToPhysFxn;
- Enet_init() to pass the OSAL and utils configurations setup in the previous two steps. The application can pass NULL to either the OSAL config or utils config if it intends to use the driver's default implementation.
Peripheral Open Sequence
This is an initialization that needs to be done for each peripheral in the system. The configuration parameters described in this section are peripheral specific.
Application should follow the next steps:
- Initialize the peripheral configuration parameters with default values using Enet_initCfg(). Although the application can fill all parameters manually, it's recommended tofirst get the driver's default values for all parameters and only overwrite the parameters of interest.
- CPSW peripheral configuration - Cpsw_Cfg structure has the configuration parameters for CPSW Enet Peripheral, such as:
- Once done with the configuration of the parameters, the UDMA driver has to be opened. Enet utils library provides a helper function called EnetAppUtils_udmaOpen() to open the UDMA driver, and returns a handle that can be passed to the peripheral configuration parameters, i.e. Cpsw_Cfg::dmaCfg.
- Enet_open() to open a peripheral, passing the configuration parameters previously initialized. Enet_open() function takes the following arguments:
- Peripheral type - This specifies the type or class of the peripheral, i.e. CPSW, ICSSG or other.
- Instance number - This argument specifies the instance number of the peripheral. Refer to Enet Peripherals section for further information about specific peripheral types and instance numbers.
- Configuration structure - A pointer to the peripheral-specific configuration structure, i.e. Cpsw_Cfg or Icssg_Cfg.
- Size of the configuration structure.
- If the module is opened successfully, the API will return a valid handle pointer to the Enet driver. It's worth noting that there will be a unique Enet handle (Enet_Handle) for each peripheral opened.
- Attach the core with the Resource Manager (RM) using ENET_PER_IOCTL_ATTACH_CORE. IOCTL. To use IOCTLs, the application must have the following:
- Valid handle to the driver.
- Core ID, which can be obtained using EnetSoc_getCoreId().
- Valid IOCTL command.
- Valid pointer to the IOCTL parameters.
- Once the application attaches the core with Resource Manager (RM), the IOCTL call will return core key which has to be used in all further RM-related calls.
- A MAC address for the host port is to be obtained using Enet utils helper function EnetAppUtils_allocMac() and the corresponding entry in the ALE table can be added using EnetAppUtils_addHostPortEntry().
- Allocate memory for Ring Accelerators, Ethernet packets, etc. Enet LLD examples use
EnetAppMemUtils to take care of all memory allocation and freeing operations. The developer can take this as reference or can implement their own memory allocation functions.
Port Open Sequence
The MAC ports can be opened in MAC-to-PHY or MAC-to-MAC mode. In MAC-to-PHY mode, Enet LLD's PHY driver state machine will be used to configure the Ethernet PHY. In MAC-to-MAC mode, the PHY driver will be bypassed entirely.
The link speed and duplexity in MAC-to-PHY can be fixed or auto-negotiated, while in MAC-to-MAC, both link speed and duplexity can be fixed only and must be provided by application.
The steps to open and configure ports in either MAC-to-PHY or MAC-to-MAC modes are shown below.
MAC-PHY link
- Set the port number in EnetPer_PortLinkCfg structure.
- Set the MAC port interface (RMII, RGMII, SGMII, etc) through the layer, sublayer and variant fields of EnetPer_PortLinkCfg::mii.
- The MAC port configuration parameters is peripheral dependent.
- CPSW MAC Port configuration:
- Use CpswMacPort_initCfg() to initialize the CPSW MAC port configuration parameters to their default values. Overwrite any parameters as needed.
- If loopback is to be enabled, set enableLoopback flag in MAC configuration to true. For loopback to be functional the secure flag in host port ALE entry must be set to false. The host port entry update can be done using the CPSW_ALE_IOCTL_ADD_UCAST command.
- Set PHY configuration parameters: generic and model specific.
- Use EnetPhy_initCfg() to initialize the PHY generic parameters to their default values, such as auto-negotiation capabilities, strap enable/disable, loopback, etc.
- Use PHY specific init config functions to initialize model specific parameters. This init config function is provided by the Ethernet PHYs supported in Enet LLD. For example, Dp83867_initCfg() is used to initialize config params for DP83867 PHYs.
- Application can also use the Enet helper function EnetBoard_getPhyCfg() to get PHY configuration information for PHYs in TI EVMs.
- Set the link speed and duplexity configuration in EnetPer_PortLinkCfg::linkCfg.
- Once all the MAC and PHY configurations are done, the ports can be opened by calling the ENET_PER_IOCTL_OPEN_PORT_LINK command.
- CPSW Note: To enable RMII on CPSW9G, external 50 MHz RMII clock from PHY is used on SOC RMII_REF_CLOCK pin. On GESI board, this clock is connected as resistor R225 is not populated. To get RMII_50MHZ_CLK, resistor R225 needs to be populated. We need to move R226 to R225 on GESI board to get this clock.
- If all the above steps succeeded without any errors, then the Enet driver, the Ethernet peripheral and a MAC port have been opened successfully.
- After opening the port, the driver will run its PHY state machine to configure the PHY and eventually get link up status. Application can query the port link using ENET_PER_IOCTL_IS_PORT_LINK_UP.
- Application can check the PHY alive status (i.e. whether PHY is present on the MDIO bus) using the ENET_MDIO_IOCTL_IS_ALIVE command.
- Once link up is detected, application should do the following steps:
The following code snippet shows how a MAC-PHY link is opened (step 1-6 above). CPSW MAC port 1 connected to a DP83867 RGMII PHY has been chosen for this example.
portLinkCfg.
macCfg = &cpswMacCfg;
MAC-to-MAC link
- Set the port number in EnetPer_PortLinkCfg::macPort.
- Set the MAC port interface (RMII, RGMII, SGMII, etc) through the layer, sublayer and variant fields of EnetPer_PortLinkCfg::mii.
- Initialize the MAC configuration parameters using CpswMacPort_initCfg() and manually overwrite any parameters that differ from defaults.
- Set PHY address to ENETPHY_INVALID_PHYADDR to indicate that this is a PHY-less connection.
- Set the link speed and duplexity configuration in EnetPer_PortLinkCfg::linkCfg to match those of the partner MAC port. The speed and duplexity must be fixed values, they can't be ENET_SPEED_AUTO or ENET_DUPLEX_AUTO as they are used for auto-negotiation which is not relevant in MAC-to-MAC mode.
- Once all the MAC and PHY configurations are done, the ports can be opened by calling the ENET_PER_IOCTL_OPEN_PORT_LINK command.
- If all the above steps succeeded without any errors, then the Enet driver, the Ethernet peripheral and a MAC port have been opened successfully.
- Once link up is detected, application should do the following steps:
The following code snippet shows how a MAC-to-MAC link is opened (steps 1-6 above). CPSW MAC port 1 connected to partner MAC using RGMII interface at 1 Gbps.
portLinkCfg.
macCfg = &cpswMacCfg;
Packet Send/Receive Sequence
- The DMA channels to enable data transfer are to be opened. It can be done using the below steps:
- Initialize the Tx Channel and Rx Flow parameters using EnetDma_initTxChParams() and EnetDma_initRxChParams(), respectively.
- For Tx Channel set the following parameters:
- EnetUdma_OpenTxChPrms::chNum: Tx Channel number.
- EnetUdma_OpenTxChPrms::hUdmaDrv: UDMA driver handle obtained before.
- EnetUdma_OpenTxChPrms::ringMemAllocFxn: EnetMem_allocRingMem. or equivalent user preferred function.
- EnetUdma_OpenTxChPrms::ringMemFreeFxn: EnetMem_freeRingMem or equivalent user preferred function.
- EnetUdma_OpenTxChPrms::numTxPkts: number of Tx packets used to alloc ring elements, and descriptors.
- EnetUdma_OpenTxChPrms::disableCacheOpsFlag: true/false.
- EnetUdma_OpenTxChPrms::dmaDescAllocFxn: EnetMem_allocDmaDesc or equivalent user preferred function.
- EnetUdma_OpenTxChPrms::dmaDescFreeFxn: EnetMem_freeDmaDesc or equivalent user preferred function.
- EnetUdma_OpenTxChPrms::cbArg: Argument to be used for the callback routines.
- For Rx Flow set the following parameters:
- EnetUdma_OpenRxFlowPrms::startIdx: Rx flow start index.
- EnetUdma_OpenRxFlowPrms::flowIdx: Rx flow number.
- EnetUdma_OpenRxFlowPrms::hUdmaDrv: UDMA driver handle obtained previously.
- EnetUdma_OpenRxFlowPrms::ringMemAllocFxn: EnetMem_allocRingMem or equivalent user preferred function.
- EnetUdma_OpenRxFlowPrms::ringMemFreeFxn: EnetMem_freeRingMem or equivalent user preferred function.
- EnetUdma_OpenRxFlowPrms::numRxPkts: number of Rx packets used to alloc ring elements, and descriptors.
- EnetUdma_OpenRxFlowPrms::rxFlowMtu: Maximum receive packet length for this flow.
- EnetUdma_OpenRxFlowPrms::disableCacheOpsFlag: true/false.
- EnetUdma_OpenRxFlowPrms::dmaDescAllocFxn: EnetMem_allocDmaDesc or equivalent user preferred function.
- EnetUdma_OpenRxFlowPrms::dmaDescFreeFxn: EnetMem_freeDmaDesc. or equivalent user preferred function.
- EnetUdma_OpenRxFlowPrms::cbArg: Argument to be used for the callback routines.
- After setting the parameters, open the channel and flow using Enet utils helper functions EnetAppUtils_openTxCh() and EnetAppUtils_openRxFlow(), respectively.
- Now that the Ethernet peripheral (CPSW or ICSSG) and UDMA are configured, the application can start the data transfer.
- To transmit data from application:
- To receive packets that are queued up in the CPSW or ICSSG hardware which are ready to be received by the application:
IOCTL Sequence
- Some common IOCTLs have already been mentioned in this document so far. But the application can run any other IOCTL supported by the peripheral. There are two kinds of IOCTLs: synchronous and asynchronous. Asynchronous IOCTLs require an additional completion poll step which is explained in Synchronous and Asynchronous IOCTLs section of the Enet LLD IOCTL interface document.
Port Close Sequence
- MAC ports that were opened earlier can be closed using ENET_PER_IOCTL_CLOSE_PORT_LINK IOCTL command. This will close the PHY state machine associated with this MAC port, if the port was not open in MAC-to-MAC mode. Application can choose to reopen the port at any time in the future by following the steps listed in Port Open Sequence section.
Peripheral Close Sequence
- Disable the host port using the ENET_HOSTPORT_IOCTL_DISABLE command
- Close the opened Tx Channel and Rx flow:
- Close the Rx flow using EnetAppUtils_closeRxFlow().
- Close the Tx Channel using EnetAppUtils_closeTxCh().
- Detach the core from Resource Manager using the ENET_PER_IOCTL_DETACH_CORE command.
- Enet driver can now be closed and de-initialized using Enet_close() and Enet_deinit().
Deinit Sequence
This is one-time deinitialization sequence that must be followed when the application no longer wants to use the Enet LLD.
- Enet_deinit() should be called to deinitialize the driver. No further Enet LLD APIs should be called from this point.
- Finally, close the UDMA driver using EnetAppUtils_udmaclose()
Back To Top
Peripheral-specific
Back To Top
1.8.20