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

• 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
Group Management
The group concept allows user to carry out operations on a group of devices conveniently. User
can freely group devices into meaningful groups so that they can be processed as a unit. For
instance, user can instantiate a “core fabric” group that contains all NSE devices in a multi-stage
fabric system.
Groups are defined by the use of the
defined, and at all times after that, the group state is determined by the states of the constituent
devices. If all devices within a certain group are in the same state, then the group is in that state as
well. If not all devices within a group are in the same state, then the group state is indeterminate.
The user can choose to use only group-based functions to initialize the chipset . If so, the group
management flow diagram is identical to the device management flow diagram shown in Figure
18, with the exception that function
the various group management functions are called, all devices within the specified group are
transitioned to the appropriate states.
However, devices may be members of multiple groups. Because of this, group states do not
always transition in the same manner as in the device state diagram. In Figure 21, say one group
(A) has been established through the use of
different, disjoint group (B) of devices has been established through the use of
nbcsInit
considered to be in the INACTIVE state. All devices in group B, as well as group B itself, are
considered to be in the ACTIVE state.
If a new group, say group C, is formed, consisting of some of group A, some of group B, and
some new devices,
INDETERMINATE; the devices within group C have states of ACTIVE, INACTIVE, or
PRESENT. Note that the USER would not be able to call
not in the PRESENT state. Rather, if the USER wants the devices with PRESENT state to
transition into the INACTIVE state, the USER must call
On the other hand, say a new group (D) is created, using only the single function
nbcsGroupAdd
brought into the ACTIVE state with device management functions. This new group is in the
ACTIVE state, since all of its devices are ACTIVE.
New devices can be added to and deleted from an existing group by calling
nbcsGroupDelete
nbcsGroupGetState.
Thus, it is most expedient to use the Group Management functions (
nbcsGroupDelete
conveniently. Later, other potentially overlapping groupings can be made, to facilitate the
commands sent during normal operation. However, the user is cautioned against using the group
functions to cause state transitions on overlapping groups.
, and
nbcsActivate
, out of part of group B and some new ACTIVE devices that were previously
nbcsGroupAdd
, etc.) on non-overlapping groups of devices, in order to initialize the devices
respectively. The state of a group can be retrieved by API function
. Now all devices in group A, as well as group A itself, are
nbcsGroupDelete
can be called to create the group. Group C now has state of
nbcsGroupAdd
nbcsGroupAdd
function call. At the time the group is
Narrowband Chipset Device Driver Manual
nbcsInit
has to be employed to delete a group. As
nbcsInit
followed by
nbcsGroupAdd
on each such device.
on group C, as group C is
nbcsInit
nbcsGroupAdd
nbcsGroupAdd
Software Architecture
, and a
,
and
52
,