Lines Matching refs:bound
379 and the specific way it is bound on a particular board.
481 specific devices are described and bound. In most circumstances we wish to
561 Device sequence numbers are resolved when a device is bound and the number does
565 since a strictly increase sequence (with devicetree nodes bound first) is not
593 children are bound and probed.
685 At this point all the devices are known, and bound to their drivers. There
687 activated (except for the root device). Each bound device that was created
689 in that declaration. For a bound device created from the device tree,
748 works the same way whether it was bound using a device tree node or
871 5. The device is marked inactive. Note that it is still bound, so the
950 property can provide better control granularity on which device is bound
952 devices with the same driver are bound, which requires allocation a large
954 only way for statically declared devices via U_BOOT_DRVINFO() to be bound
960 which means that it will be processed (and a driver bound) in U-Boot proper
965 device trees (see README.SPL for details); the remaining nodes are always bound.