Lines Matching refs:uclass

22 Uclass - a group of devices which operate in the same way. A uclass provides
24 	using the same interface. For example a GPIO uclass provides
25 	operations for get/set value. An I2C uclass may have 10 I2C ports,
46 There is a uclass called 'demo'. This uclass handles
48 uclass:
90 in sandbox, and every uclass has its own test. As a move towards this, tests
240 This function looks up a device for the demo uclass. Given a device
242 the UCLASS_DEMO uclass.
250 This function is in the demo uclass. It takes care of calling the 'hello'
254 The code for demo_hello() is in drivers/demo/demo-uclass.c:
456 The demo uclass is declared like this:
462 It is also possible to specify special methods for probe, etc. The uclass
463 numbering comes from include/dm/uclass.h. To add a new uclass, add to the
464 end of the enum there, then declare your uclass as above.
474 device in its uclass, so no two devices within a particular uclass can have
488 used. Make sure that the uclass has the DM_UC_FLAG_SEQ_ALIAS flag set.
494 This indicates that in the uclass called "serial", the named node
530 to the methods the uclass driver provides. Thirdly, per-child platform data
534 For consistency and ease of implementation, the bus uclass can specify the
536 in that uclass. There are also uclass methods which can be called when
539 Here an explanation of how a bus fits with a uclass may be useful. Consider
541 up) uclass:
553 three children. This can be auto-allocated if the bus driver (or bus uclass)
555 the bus device or uclass can allocate the space itself before the child
562 Similarly the bus uclass can define the child_post_bind() method to obtain
564 The bus uclass can also provide a child_pre_probe() method. Very often it is
565 the bus uclass that controls these features, since it avoids each driver
592 The uclass for the device can also contain data private to that uclass.
594 uclass, and this data has nothing to do with the child data for each child
595 on the bus. It is the bus' uclass that controls the child with respect to
624 uclass & driver, initializes any optional fields of the device object that are
634 node that caused the device to be created. The uclass is set correctly for
664    c. If the device's uclass specifies a non-zero per_device_auto_alloc_size,
666    stored in the device, but it is uclass data. owned by the uclass driver.
709       - uclass data in dev->uclass_priv (for things the uclass stores
718    j. The uclass's post_probe() method is called, if one exists. This may
719    cause the uclass to do some housekeeping to record the device as
720    activated and 'known' by the uclass.
726 uclass's list of devices (so if the device is in UCLASS_GPIO it will appear
727 as a device in the GPIO uclass). This is the 'running' state of the device.
734    a. The uclass's pre_remove() method is called, if one exists. This may
735    cause the uclass to do some housekeeping to record the device as
736    deactivated and no-longer 'known' by the uclass.
743    deallocated so platform data, private data and the uclass data will all
749    d. The device memory is freed (platform data, private data, uclass data,
805 - Change the name 'core' to 'uclass', meaning U-Boot class. It seems that
807 use 'class' since it is a C++ reserved word, so U-Boot class (uclass) seems
859 support, a uclass is created and a CONFIG to enable use of driver model for
881 be fewer merge conflicts in uclass-id.h.