Lines Matching refs:consumer

30 "supplier" device and its "consumer" devices, and it guarantees driver
31 presence on the supplier.  The consumer devices are not probed before the
43 whenever and for as long as the consumer is runtime resumed.
50 :c:func:`device_initialize()` has been called for the consumer.
61 represents a driver presence dependency, yet is added from the consumer's
64 consumer in the first place.  The onus is thus on the consumer to check
69 consumer driver, it is typically deleted in its ``->remove`` callback for
82 link is added from the consumer's ``->probe`` callback:  ``DL_FLAG_RPM_ACTIVE``
85 automatically purged when the consumer fails to probe or later unbinds.
98 the consumer to be deferred indefinitely.  This can become a problem if the
99 consumer is required to probe before a certain initcall level is reached.
100 Worse, if the supplier driver is blacklisted or missing, the consumer will
125   runtime PM integration is added from the busmaster device (consumer)
150   VGA device.  A device link from the HDA controller (consumer) to the
195 To ensure this, upon addition of the device link the consumer and the
196 entire sub-graph below it (all children and consumers of the consumer)
202 on the consumer or any children or consumers of the consumer.
236   and consumer.  If the link is created before any devices are probed, it
244 * Before a consumer device is probed, presence of supplier drivers is
259 * When the consumer's driver is later on removed, links to suppliers revert