Lines Matching +full:re +full:- +full:started

31 supplier is bound to a driver, and they're unbound before the supplier
57 device ``->probe`` callback or a boot-time PCI quirk.
61 ``->probe`` callback while the supplier hasn't started to probe yet:  Had the
65 non-presence.  [Note that it is valid to create a link from the consumer's
66 ``->probe`` callback while the supplier is still probing, but the consumer must
72 is added in the ``->probe`` callback of the supplier or consumer driver, it is
73 typically deleted in its ``->remove`` callback for symmetry.  That way, if the
87 link is added from the consumer's ``->probe`` callback:  ``DL_FLAG_RPM_ACTIVE``
93 Similarly, when the device link is added from supplier's ``->probe`` callback,
125 :c:func:`device_link_add()` may cause the PM-runtime usage counter of the
129 called twice in a row for the same consumer-supplier pair without removing the
130 link between these calls, in which case allowing the PM-runtime usage counter
132 suspended while the consumer is still PM-runtime-active and that has to be
135 it with PM-runtime disabled, between the :c:func:`device_link_add()` and
142 resources at probe time but on non-presence there is no way to know whether
173   the NHI device needs to re-establish PCI tunnels to attached devices
176   PM core, but unfortunately they're aunts.  The solution is to add
217 The device hierarchy, which -- as the name implies -- is a tree,
222 no device links present, the two lists are a flattened, one-dimensional
225 or OpenFirmware device tree top-down and appending devices to the lists
231 entire sub-graph below it (all children and consumers of the consumer)
256 .. kernel-doc:: include/linux/device.h