PMC-Sierra PM5358 S/UNI 4x622 Procedure 2: Porting Drivers to Hardware Platforms, Procedure 3: Porting Driver Application-Specific Elements

PM5358 S/UNI-4x622 Driver Manual
Porting the S/UNI-4x622 Driver
Proprietary and Confidential to PMC-Sierra, Inc. 119
Document ID: PMC-2010419, Issue 1
sysSuni4x622ISRHandlerIntInstall In stalls the in ter rup t handler
for the OS
sysSuni4x622ISRHandlerRemove Removes the interrupt
handler from the OS
sysSuni4x622ISRHandler Interrupt handler for the
S/UNI-4x622 device
Interrupt
sysSuni4x622DPRTask Deferred inter rup t-proces sing
routine (DPR)
Procedure 2: Porting Drivers to Hardware Platforms
This section describes how to modify the driver for your hardware platform.
To port the driver to your hardware platform:
1. Modify the low-level device read/write macros in the suni4x622_hw.h file. You may need
to modify the raw read/write access macros (sysSuni4x622ReadReg and
sysSuni4x622WriteReg) to reflect your system’s addressing logic.
2. Define the hardware system-configuration constants in the suni4x622_hw.h file. Modify
the following constants to reflect your system’s hardware configuration:
Device Constant Description Default
SUNI4x622_MAX_DEVS The maximum number of S/UNI-4x622 devices on each
card 5
Procedure 3: Porting Driver Application-Specific Elements
Application specific elements are configuration constants used by the API for developing an
application. This section describes how to modify the application specific elements in the driver.
To port the driver’s application-specific elements:
1. Define the following driver task-related constants for your OS-specific services in file
suni4x622_hw.h and suni4x622_rtos.h:
Task Constant Description Default
SUNI4x622_DPR_TASK_PRIORITY Deferred Task (DPR) task priority 85