P4080 PCIe Adapter SDK User Guide Production Release

Freescale Semiconductor
hw_data – Hardware function specific data that is exchanged with the P4080 Packet
Driver.
struct hw_fn_data {
};
hw_fn_tx_cb tx_cb;
hw_fn_cmd_cb cmd_cb;
The prototype of Tx and command ring callback functions are as follows
typedef int (*hw_fn_tx_cb)(struct qm_fd *fd, int cpu_id, int ring_id);
typedef int (*hw_fn_cmd_cb)(struct p4080_fd *fd);
/**
* Callback: hw_fn_tx_cb : Callback function that is registered with PCIe
* Driver and is invoked in dma_channel_poll() API when DMA transfer for
* a Tx packet is successful
*
* @qm_fd – Qman FD that has to be enqueued into one of the
* Tx Frame Queues.
* @cpu_id – Core on which the Tx packet has come. This is used to select
* the Tx Frame
* Queue.
* @ring_id – Used as an index into flow table to get the Frame Queue ID
* and Ethernet port ID.
*
* @return - SUCCESS (0) on successful registration otherwise ERROR (1)
*/
/**
* Callback: hw_fn_cmd_cb : Callback function that is registered with PCIe
* Driver and is invoked in pkt_drv_process_command_ring() API when a
* command is received from Host Packet Driver or Host Hardware Function
* Driver.
*
* @p4080_fd– P4080 FD that holds command data
*
* @return - SUCCESS (0) on successful registration otherwise ERROR (1)
*/
/**
* API: pkt_drv_unregister_hw_function : Each Hardware Function has to
* unregister with PCIe Driver using this API. This API has to be
* invoked in the context of Hardware Function cleanup
* function (such hw_fn_clean_eth()). This API clears the Tx callback
* function and command callback function of the PCIe Driver context.
© Freescale Semiconductor, Inc., 2011. All rights reserved.
Freescale Confidential Proprietary Page 55