Lines Matching refs:method

251 method of the relevant driver. Bearing in mind that there are two drivers,
266 As you can see it just calls the relevant driver method. One of these is
432 and zeroed before the driver's ofdata_to_platdata() method is called. The
433 ofdata_to_platdata() method, which the driver write supplies, should parse
435 when the probe method is called later (to set up the device ready for use)
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
445 in your ofdata_to_platdata (or probe) method to allocate the required memory,
446 and you should free it in the remove method.
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
603 methods mentioned here are optional - e.g. if there is no probe() method for
626 driver's bind() method if one is defined.
637 The device's bind() method is permitted to perform simple actions, but
640 the probe() method.
685    g. If the driver provides an ofdata_to_platdata() method, then this is
701    h. The device's probe() method is called. This should do anything that
714    platdata_auto_alloc_size. Remember to free them in the remove() method.
718    j. The uclass's post_probe() method is called, if one exists. This may
734    a. The uclass's pre_remove() method is called, if one exists. This may
742    c. The device's remove() method is called. At this stage nothing has been
753    static pointer, it is not de-allocated during the remove() method. For
756    remove() method, either: