Lines Matching refs:structure

312 The U_BOOT_DRIVER macro creates a data structure accessible from C,
332 *** basically a C structure which is passed to drivers to tell them about
355 gives the driver name and a pointer to a structure containing information
373 Where does the platform data come from? It is either held in a structure
618 and uses the of_match table of the U_BOOT_DRIVER() structure to find the
690    using a device tree node or U_BOOT_DEVICE() structure. In either case,
691    the platform data is now stored in the platdata structure. Typically you
693    platform data structure, and U-Boot will automatically allocate and zero
773    device structure itself is not freed at this point. Should the device be
786 Driver model uses a doubly-linked list as the basic data structure. Some
788 data structure might be worthwhile in some rare cases, once we understand
800 - Moved some data from code into data structure - e.g. store a pointer to
801 the driver operations structure in the driver, rather than passing it