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

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

3.3
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-1991611, Issue 2
Present: TMX_PRESENT
This device state is a quiet state for the device. In order to get to this state, the API needs to be
called by one of two functions:
·
·
Active: TMX_ACTIVE
This is the normal operating state for the device(s). State changes can be initiated from the active
state via
Inactive: TMX_INACTIVE
This state is entered via the
device remains configured but all data functions are de-activated including interrupts and status,
alarms, and counter functions.
temuxReset
Processing Flows
The flow diagrams presented here illustrate the sequence of operations that take place for
different driver functions. The diagrams also serve as a guide to the application programmer by
illustrating the sequence in which the application must invoke the driver API.
Module Management
The following flow diagram illustrates the typical function call sequences that occur when
initializing or shutting down the TEMUX/TEMAP/TECT3 driver module.
In this state, devices can be initialized via
temuxAdd
structures associated with this device.
temuxReset
initialized condition.
temuxDelete
or
: Responsible for verifying the presence of the device and for initializing the data
temuxDelete
: De-activates the device and restores the device’s data structures to the
,
temuxDeActivate
temuxDeActivate
temuxActivate
will de-configure the device.
TEMUX/TEMAP/TECT3 (PM8315, PM5365, PM4328) Driver Manual
temuxInit
and
or
will return the device to the active state, while
temuxReset
temuxInit
or deleted via
.
function calls. In this state the
temuxDelete
Software State Description
.
20