Filter
Top Products
PM5358 S/UNI-4x622 Driver Manual
Data Structures
Proprietary and Confidential to PMC-Sierra, Inc. 50
Document ID: PMC-2010419, Issue 1
Field Name Field Type Field Description
rxfprminlf UINT2
Rx minimum length error frame count
rxfprmaxlf UINT2
Rx maximum length error frame count
txfptbyte UINT4
Tx byte count
txfptframe UINT4
Tx frame count
txfptusrabf UINT4
Tx user aborted frame count
txfptferabf UINT4
Tx underrun/error aborted frame count
3.4 Structures Passed through RTOS Buffers
Interrupt-Service Vector: ISV
This buffer structure is used to capture the status of the device (during a poll or ISR processing)
for use by the Deferred-Processing Routine (DPR). It is the template for all device registers that
are involved in exception processing. It is the application’s responsibility to create a pool of ISV
buffers (using this template to determine the buffer’s size) when the driver calls the USER-
supplied
sysSuni4x622BufferStart function. An individual ISV buffer is then obtained by
the driver via
sysSuni4x622ISVBufferGet and returned to the ‘pool’ via
sysSuni4x622ISVBufferRtn.
Table 36: S/UNI-4x622 Interrupt-Service Vector: sSUNI4x622_ISV
Field Name Field Type Field Description
deviceHandle sSUNI4x622_HNDL
Handle to the device in cause
mask sSUNI4x622_MASK_ISR
ISR mask filled with interrupt status
Deferred-Processing Vector: DPV
This block is used in two ways. First it is used to determine the size of buffer required by the
RTOS for use in the driver. Second it is the template for data that is assembled by the DPR and
sent to the application code. Note: the application code is responsible for returning this buffer to
the RTOS buffer pool.
The DPR reports events to the application using user-defined callbacks. The DPR uses each
callback to report a functionally-related group of events. Refer to page 104 for a description of
the S/UNI-4x622 callback functions, and Appendix C (page 126) for a list of events.