Lines Matching +full:enforce +full:- +full:video +full:- +full:mode

18 Secondly, the driver core by default does not enforce any driver presence
58 device ``->probe`` callback or a boot-time PCI quirk.
62 ``->probe`` callback while the supplier hasn't started to probe yet:  Had the
66 non-presence.  [Note that it is valid to create a link from the consumer's
67 ``->probe`` callback while the supplier is still probing, but the consumer must
73 is added in the ``->probe`` callback of the supplier or consumer driver, it is
74 typically deleted in its ``->remove`` callback for symmetry.  That way, if the
88 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 in a degraded mode (reduced feature set or performance) when those resources
127 or work in PIO mode.  The controller can determine presence of the optional
128 resources at probe time but on non-presence there is no way to know whether
159   the NHI device needs to re-establish PCI tunnels to attached devices
180 * In some SoCs a functional dependency exists from display, video codec and
181   video processing IP cores on transparent memory access IP cores that handle
193   suspended.  Furthermore it cannot be used to enforce a specific shutdown
203 The device hierarchy, which -- as the name implies -- is a tree,
208 no device links present, the two lists are a flattened, one-dimensional
211 or OpenFirmware device tree top-down and appending devices to the lists
217 entire sub-graph below it (all children and consumers of the consumer)
242 .. kernel-doc:: include/linux/device.h
305 .. kernel-doc:: drivers/base/core.c