PM8621-BI PMC-Sierra, Inc., PM8621-BI Datasheet - Page 54

• Manufacturer Part Number: PM8621-BI
• Description: Driver, NSE/SBS Narrowband Chipset Driver
• Manufacturer: PMC-Sierra, Inc.

Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-2021248, Issue 1
2) (Defining the payload types) API function
3) (Put the system in loopback state). The loopback state is the point of reference for the system,
4) (Setting up egress bus integrity for SBS/SBSLITE revision B devices only). As soon as the
SBS and NSE devices can be present locally or remotely depending on the system configuration,
In a typical centralized system configuration, all devices are local and are under the control of a
microprocessor that also runs the CSD. In a distributed system configuration, SBS and NSE
devices that make up the switching fabric may be scattered across line, core or standalone
processor cards and are under the control of multiple microprocessors. The CSD can be
configured to run in all the cards with any combination of SBS/NSE devices present locally to the
card.
In a typical centralized configuration, NSE/SBS devices are present and the OPA is expected to
perform the routing; hence, the following fields in the
and
physical NSE devices nor will it run the OPA routing; hence, the following fields in the
sbsDrvPresent
Likewise, in a typical core card configuration, the fields
should be set to 0 and 1 respectively. The field
whether the OPA routing is run locally or elsewhere. In a typical standalone system that is
intended to host the CSD with the OPA,
should then be set to 0, 0 and 1 respectively since the SBS and NSE device drivers are absent.
There should only be one CSD module in the system with the field
SBS devices that are not physically attached to the CSD-distributed-core or CSD-standalone do
have to be added even in the distributed core or standalone CSD. This creates a logical proxy of
the actual remote SBS on the side of the distributed-core/standalone CSD. However, note that the
NSE devices do not have to be added on the remote CSD side.
payload type of the SBS, for both the ingress and egress sides. The same function is used
regardless of what bus mode the system is set to, SBI336 or TeleCombus. In the case of SBI
bus, further tributaries configuration can be carried out using API
function is not applicable when the system is configured to TeleCombus mode.
which then evolves from this point with the addition of connections, etc… All the traffic is
being looped back at this state. User should call the API function
which
connections to support the loopback mode. User should then perform a synchronized page
switch to put the settings in effect. Please refer to the subsequent section for more details on
this operation.
payload types are defined for all SBS devices, the egress bus integrity can be set up prior to
any call activities. Preserving the bus integrity for each outgoing SPE is essential to the
downstream device. For example, the J1 byte in each SPE has to be set up properly; the V1
byte has to be valid in a T1 or E1 tributary inside the SPE, etc. The function
nbcsFmgtUnMapTrib
properly defined). The side effect is all data in the payload is overwritten by zero and the
loopback state will be disturbed. This step is optional.
opaLibUse
updates the offline page of all the local devices and resets the OPA library to clear all
should all be set to 1. In a typical line card, it is not expected to contain any
,
nseDrvPresent
is used to setup the integrity (as long as the SPE types have been
, and
sbsDrvPresent
opaLibUse
opaLibUse
nbcsIntfCfgPyld
MIV sbsDrvPresent
should be set to 1, 0, and 0 respectively.
sbsDrvPresent
Narrowband Chipset Device Driver Manual
,
nseDrvPresent
can be either 0 or 1 depending on
opaLibUse
is used to configure the
nbcsFmgtSetLpbkMode,
nbcsIntfCfgTrib.
, and
,
, and
nseDrvPresent
Software Architecture
nseDrvPresent
set to 1.
opaLibUse
MIV
This
54
,
,