Lines Matching refs:it
29 interface to it.
34 How to try it
37 Build U-Boot sandbox and run it:
53 The demo class is pretty simple, but not trivial. The intention is that it
54 can be used for testing, so it will implement all driver model features and
55 provide good code coverage of them. It does have multiple drivers, it
57 to operate on a particular platform) and it uses private driver data.
59 To try it, see the example session below:
266 As you can see it just calls the relevant driver method. One of these is
281 but it leaves a lot of topics to address.
308 In U_BOOT_DRIVER it is also possible to specify special methods for bind
310 it is hoped that only 'probe' and 'remove' will be needed.
318 bind - make the driver model aware of a device (bind it to its driver)
322 remove - remove a device so it cannot be used until probed again
346 highly-complex SoCs it is common for the IP to come from an IP vendor, and
353 Using the UART example, we have a single driver and it is instantiated 6
361 a device, but needs to know where it is, any variant/option information and
363 and the specific way it is bound on a particular board.
374 which is compiled into U-Boot, or it can be parsed from the Device Tree
377 For an example of how it can be compiled in, see demo-pdata.c which
379 The data can be interpreted by the drivers however they like - it is
426 The easiest way to make this work it to add a few members to the driver:
434 the device tree node for this device and place it in dev->platdata. Thus
439 method then it will be called first (during activation). If you provide a
440 probe method it will be called next. See Driver Lifecycle below for more
446 and you should free it in the remove method.
480 cases. While it might be tempting to automatically renumber the devices
523 the bus provides some sort of transport or translation that makes it
535 per-child platform data, so that it can be the same for all children of buses
540 a USB bus with several devices attached to it, each from a different (made
559 methods to allow it to do some processing before the child is activated or
560 after it is deactivated.
563 the per-child platform data from the device tree and set it up for the child.
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
570 driver, not the child's. In fact it is possible that child has no knowledge
571 that it is connected to a bus. The same child device may even be used on two
604 a device then it will not be called. A simple device may have very few
644 U-Boot it may be expensive to probe devices and we don't want to do it until
649 When a device needs to be used, U-Boot activates it, by following these
654 dev->priv. The driver can put anything it likes in there, but should use
655 it for run-time information, not platform data (which should be static
666 stored in the device, but it is uclass data. owned by the uclass driver.
667 It is possible for the device to access it.
689 After this point, the device works the same way whether it was bound
694 it for you before entry to ofdata_to_platdata(). But if not, you can
695 allocate it yourself in ofdata_to_platdata(). Note that it is preferable
698 data, one day it is possible that U-Boot will cache platformat data for
702 is required by the device to get it going. This could include checking
724 The device is now activated and can be used. From now until it is removed
726 uclass's list of devices (so if the device is in UCLASS_GPIO it will appear
732 remove it. This performs the probe steps in reverse:
746 to be sure that no hardware is running, it should be enough to remove
753 static pointer, it is not de-allocated during the remove() method. For
765 e. The device sequence number is set to -1, meaning that it no longer
767 sequence number is still free, it may well receive the name sequence
772 f. The device is marked inactive. Note that it is still bound, so the
801 the driver operations structure in the driver, rather than passing it
807 use 'class' since it is a C++ reserved word, so U-Boot class (uclass) seems
812 - Removed the concept of driver relocation, and just make it possible for
816 dealing with this might not be worth it.
817 - Implemented a GPIO system, trying to keep it simple