Lines Matching refs:supplier

30 "supplier" device and its "consumer" devices, and it guarantees driver
31 presence on the supplier.  The consumer devices are not probed before the
32 supplier is bound to a driver, and they're unbound before the supplier
35 When driver presence on the supplier is irrelevant and only correct
38 enforcing driver presence on the supplier is optional.
42 is instructed to runtime resume the supplier and keep it active
49 :c:func:`device_add()` has been called for the supplier and
62 ``->probe`` callback while the supplier hasn't probed yet:  Had the driver
65 presence of the supplier after adding the link, and defer probing on
68 If a device link is added in the ``->probe`` callback of the supplier or
83 can be specified to runtime resume the supplier upon addition of the
89 Similarly, when the device link is added from supplier's ``->probe`` callback,
91 purged when the supplier fails to probe or later unbinds.
100 Worse, if the supplier driver is blacklisted or missing, the consumer will
108 they will become available in the near future (due to a supplier driver
126   to the MMU device (supplier).  The effect with regards to runtime PM
143   (supplier).  A driver presence dependency is not necessary for this
151   VGA device (supplier) aptly represents this relationship.
201 verified upon device link addition that the supplier is not dependent
235   :c:func:`device_link_add()` based on the driver presence on the supplier
239 * When a supplier device is bound to a driver, links to its consumers
244 * Before a consumer device is probed, presence of supplier drivers is
249   This prevents the supplier from unbinding.
265 * Before a supplier's driver is removed, links to consumers that are not
277   the supplier driver is released and the links revert to ``DL_STATE_DORMANT``.