Lines Matching refs:inbound
83 state value into two parts (the "cluster" state and "inbound" state) and
206 as seen by a CPU tearing the cluster down. The "inbound side" is the
221 "inbound" state: The state of the cluster on the inbound side.
250 Transitions ===##> can only be made by the inbound CPU, and only
251 involve changes to the "inbound" state, except where there is no
264 The parallelism of the inbound and outbound CPUs is observed by
280 <cluster state>/<inbound state> (<transitioner>)
283 can occur; either the inbound or the outbound side.
288 Next state: CLUSTER_DOWN/INBOUND_COMING_UP (inbound)
300 In this state, an inbound CPU sets up the cluster, including
309 Next state: CLUSTER_UP/INBOUND_COMING_UP (inbound)
324 Next state: CLUSTER_UP/INBOUND_NOT_COMING_UP (inbound)
354 should check the inbound cluster state for asynchronous
365 CLUSTER_GOING_DOWN/INBOUND_COMING_UP (inbound)
388 in the CLUSTER_DOWN state; the inbound CPU will
414 The CPU which performs cluster setup on the inbound side is commonly
451 arch/arm/common/mcpm_head.S (low-level inbound CPU operations) and