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

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

3.5
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-1991611, Issue 2
Then
specific interrupt condition detected. The nature of this processing can differ from system to
system. Therefore,
conditions.
Typically, you should implement these callback functions as simple message posting functions
that post messages to an application task. However, you can implement the indication callback to
perform processing within the DPR task context and return without sending any messages. In this
case, ensure that the indication function does not call any API functions that change the driver’s
state, such as
customize these callbacks to suit your system.
Note: Since the
mechanism, you have full flexibility in choosing a communication mechanism between the two.
A convenient way to implement this communication mechanism is to use a message queue, which
is a service that most RTOSs provide.
You must implement the two system specific functions,
sysTemuxDPRTask
the driver installs
sysTemuxDPRTask
The
sysTemuxISRHandler
commonly a message queue associated with the
Similarly, during removal of interrupts, the driver removes
microprocessor’s interrupt vector table when
As a reference, this manual provides example implementations of the interrupt installation and
removal functions on page 81. You can customize these prototypes to suit your specific needs.
Polling Servicing
Instead of using an interrupt service model, you can use a polling service model in the
TEMUX/TEMAP/TECT3 driver to process the device’s event-indication registers.
Figure 7 illustrates the polling service model used in the TEMUX/TEMAP/TECT3 driver design.
Figure 7: Polling Service Model
sysTemuxISRHandlerInstall
temuxDPR
temuxDelete
temuxISR
processes the status information and takes appropriate action based on the
sysTemuxISRHandler
temuxDPR
. When the driver calls
function is spawned as a task when
temuxDPR
and
and
. Also, ensure that the indication function is non-blocking. You can
sysTemuxDPRTask
calls different indication callbacks for different interrupt
temuxDPR
TEMUX/TEMAP/TECT3 (PM8315, PM5365, PM4328) Driver Manual
function also creates the communication channel between
Callbacks
Indication
in the interrupt vector table of the processor. The
routines themselves do not specify a communication
sysTemuxISRHandlerInstall
sysTemuxDPRTaskRemove
sysTemuxDPRTask
. This communication channel is most
sysTemuxISRHandler
sysTemuxDPRTaskInstall
sysTemuxISRHandler
Application
.
Software State Description
is called.
for the first time,
and
from the
is called.
24