PM5365 PMC-Sierra, Inc., PM5365 Datasheet - Page 16

• Manufacturer Part Number: PM5365
• Description: TEMUX/TEMAP/TECT3 T1/E1 FRAMER, VT/TU MAPPER, M12/M13 MUX DRIVER MANUAL
• Manufacturer: PMC-Sierra, Inc.

Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-1991611, Issue 2
·
·
Driver API
The driver API consists of functions used to configure and monitor the various subsystems in the
TEMUX/TEMAP/TECT3 device. The API functions are divided into following sections:
Alarms, Status, and Statistics Section
This section is responsible for monitoring alarms, tracking devices status information and
retrieving performance and error statistics for each device registered with (added to) the driver.
Diagnostics Section
This section is responsible for providing access to the diagnostic capabilities of the
TEMUX/TEMAP/TECT3 devices. Functions are provided to various loopback modes and to test
register accesses.
Device Read/Write Section
This section provides read/write access functions to the various sub-blocks of the
TEMUX/TEMAP/TECT3 devices. Functions are provided to write to the T1/E1 framer block,
SONET/SDH Mapper block, and the DS3 Mux/Demux block. Functions are also provided to read
a block of registers and access the indirect registers.
Driver Library
The driver library module is a collection of low-level utility functions that manipulate the device
registers and the contents of the driver’s DDB. The driver library functions serve as building
blocks for higher level functions that constitute the driver API module. Application software does
not normally call the driver library functions.
Interrupt Processing
The TEMUX/TEMAP/TECT3 driver provides an ISR called
any valid interrupt conditions present for the device. This function can be used by a
system-specific interrupt-handler function to service interrupts raised by the device. Its main
purpose is to collect information about the current interrupt condition of the device and pass this
information along to the Deferred-Processing Routine for actual processing.
The low-level interrupt-handler function that traps the hardware interrupt and calls
system and RTOS dependent. Therefore, it is outside the scope of the driver. Example
implementations of an interrupt handler and functions that install and remove it are provided as a
reference on page 69. You can customize these example implementations to suit your specific
needs.
Callback function pointers
Statistical counts
TEMUX/TEMAP/TECT3 (PM8315, PM5365, PM4328) Driver Manual
temuxISR
that checks if there are
Software Architecture
temuxISR
16
is