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

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

3.2
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-1991611, Issue 2
Start: TMX_MOD_START
The TEMUX/TEMAP/TECT3 driver module has not been initialized. The only API function that
will be accepted in this state is
RTOS resources (memory, timers, etc), has no running tasks, and performs no actions.
Idle: TMX_MOD_IDLE
The TEMUX/TEMAP/TECT3 driver module has been initialized successfully via the API
function
Module Data Block (MDB) has been allocated and loaded with current data, the per-device data
structures have been allocated, and the RTOS has responded without error to all the requests sent
to it by the driver. The only API functions that will be accepted in this state are
temuxModuleStart
Ready: TMX_MOD_READY
This is the normal operating state for the driver module. This means that the RTOS resources
have been allocated and the driver is ready for devices to be added. In order to get to this state,
the API function
allocating all of the RTOS resources necessary for the proper operation of the module and the
devices). The API functions accepted here for module control are
temuxModuleClose
Devices can be added via
Once the driver module has progressed into the READY state, the user can begin to add
individual devices into operation. The driver module remains in the READY state while devices
are in operation. Devices can be added via
and
and if used, will cause each and every device (that is not in the START state) to be deleted, before
that module function is fully executed.
The following is a description of the TEMUX/TEMAP/TECT3 driver device states:
Start: TMX_START
The TEMUX/TEMAP/TECT3 driver device has not been initialized. The only API function that
will be accepted in this state is
performs no actions. There is a separate flow for each device that can be added and they all start
here.
Device States
temuxModuleClose
temuxModuleOpen
temuxModuleStart
. The driver module remains in this state while devices are in operation.
and
temuxAdd
temuxModuleClose
are always available in this state (and therefore not mentioned below)
. The Module Initialization Vector (MIV) has been validated, the
temuxModuleOpen
temuxAdd
TEMUX/TEMAP/TECT3 (PM8315, PM5365, PM4328) Driver Manual
.
is called (this function is responsible for creating and/or
. In this state, the device is unknown by the driver and
temuxAdd
.
. In this state the driver does not hold any
. The module functions
temuxModuleStop
Software State Description
temuxModuleStop
and
19