Lines Matching refs:objects

26 network ports to create functional objects/devices such as network
29 which DPAA2 software drivers use to operate on DPAA2 objects.
71 DPIO objects.
76 The section provides a brief overview of some key DPAA2 objects.
77 A simple scenario is described illustrating the objects involved
84 types of DPAA2 objects.  In the example diagram below there
85 are 8 objects of 5 types (DPMCP, DPIO, DPBP, DPNI, and DPMAC)
105 of the DPRC, discover the hardware objects present (including mappable
118 Hardware objects can be created and destroyed dynamically, providing
119 the ability to hot plug/unplug objects in and out of the DPRC.
124 All objects in a container share the same hardware "isolation context".
129 DPRCs can be defined statically and populated with objects
138 utilizing multiple hardware objects.  Each object provides specialized
139 functions. Groups of these objects are used by software to provide
144 The diagram below shows the objects needed for a simple
170 Below the objects are described.  For each object a brief description
224 objects.
232 Some objects have explicit relationships that must
261 All interrupts generated by DPAA2 objects are message
267 In the case of DPAA2 devices/objects, all objects in the
280 types of DPAA2 objects.  It is functionally similar to a plug-and-play
284 scenario and the objects bound to each driver.  A brief description
347 The DPRC driver is bound to DPRC objects and does runtime management
354 Certain objects such as DPMCP and DPBP are generic and fungible,
362 and those objects are bound to the allocator when the bus is probed.
363 The allocator maintains a pool of objects that are available for
368 The DPIO driver is bound to DPIO objects and provides services that allow
370 their respective objects.