Lines Matching refs:uclass

26   a group of devices which operate in the same way. A uclass provides
28   using the same interface. For example a GPIO uclass provides
29   operations for get/set value. An I2C uclass may have 10 I2C ports,
52 There is a uclass called 'demo'. This uclass handles
54 uclass:
96 in sandbox, and every uclass has its own test. As a move towards this, tests
248 This function looks up a device for the demo uclass. Given a device
250 the UCLASS_DEMO uclass.
260 This function is in the demo uclass. It takes care of calling the 'hello'
264 The code for demo_hello() is in drivers/demo/demo-uclass.c:
488 The demo uclass is declared like this:
496 It is also possible to specify special methods for probe, etc. The uclass
497 numbering comes from include/dm/uclass.h. To add a new uclass, add to the
498 end of the enum there, then declare your uclass as above.
508 device in its uclass, so no two devices within a particular uclass can have
522 used. Make sure that the uclass has the DM_UC_FLAG_SEQ_ALIAS flag set.
530 This indicates that in the uclass called "serial", the named node
568 to the methods the uclass driver provides. Thirdly, per-child platform data
572 For consistency and ease of implementation, the bus uclass can specify the
574 in that uclass. There are also uclass methods which can be called when
577 Here an explanation of how a bus fits with a uclass may be useful. Consider
579 up) uclass::
591 three children. This can be auto-allocated if the bus driver (or bus uclass)
593 the bus device or uclass can allocate the space itself before the child
600 Similarly the bus uclass can define the child_post_bind() method to obtain
602 The bus uclass can also provide a child_pre_probe() method. Very often it is
603 the bus uclass that controls these features, since it avoids each driver
630 The uclass for the device can also contain data private to that uclass.
632 uclass, and this data has nothing to do with the child data for each child
633 on the bus. It is the bus' uclass that controls the child with respect to
663 uclass & driver, initializes any optional fields of the device object that are
673 node that caused the device to be created. The uclass is set correctly for
704    3. If the device's uclass specifies a non-zero per_device_auto_alloc_size,
706    stored in the device, but it is uclass data. owned by the uclass driver.
749       - uclass data in dev->uclass_priv (for things the uclass stores
758    10. The uclass's post_probe() method is called, if one exists. This may
759    cause the uclass to do some housekeeping to record the device as
760    activated and 'known' by the uclass.
767 uclass's list of devices (so if the device is in UCLASS_GPIO it will appear
768 as a device in the GPIO uclass). This is the 'running' state of the device.
776    1. The uclass's pre_remove() method is called, if one exists. This may
777    cause the uclass to do some housekeeping to record the device as
778    deactivated and no-longer 'known' by the uclass.
785    deallocated so platform data, private data and the uclass data will all
791    4. The device memory is freed (platform data, private data, uclass data,
848 - Change the name 'core' to 'uclass', meaning U-Boot class. It seems that
850   use 'class' since it is a C++ reserved word, so U-Boot class (uclass) seems
917 support, a uclass is created and a CONFIG to enable use of driver model for
939 be fewer merge conflicts in uclass-id.h.