Skip to content
Snippets Groups Projects
Select Git revision
0 results

device.c

Forked from Reform / reform-boundary-uboot
Loading
  • Simon Glass's avatar
    20af3c0a
    dm: core: Call uclass post_bind() after the driver's bind() method · 20af3c0a
    Simon Glass authored
    
    At present the uclass's post_bind() method is called before the driver's
    bind() method. This means that the uclass cannot use any of the information
    set up by the driver. Move it later in the sequence to permit this.
    
    This is an ordering change which is always fairly major in nature. The main
    impact is that devices which have children will not see them appear in their
    bind() method. From what I can see, existing drivers do not look at their
    children in the bind() method, so this should be safe.
    
    Conceptually this change seems to result in a 'more correct' ordering, since
    the uclass (which is broader than the device) gets the last word.
    
    Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    Reviewed-by: default avatarTom Rini <trini@konsulko.com>
    20af3c0a
    History
    dm: core: Call uclass post_bind() after the driver's bind() method
    Simon Glass authored
    
    At present the uclass's post_bind() method is called before the driver's
    bind() method. This means that the uclass cannot use any of the information
    set up by the driver. Move it later in the sequence to permit this.
    
    This is an ordering change which is always fairly major in nature. The main
    impact is that devices which have children will not see them appear in their
    bind() method. From what I can see, existing drivers do not look at their
    children in the bind() method, so this should be safe.
    
    Conceptually this change seems to result in a 'more correct' ordering, since
    the uclass (which is broader than the device) gets the last word.
    
    Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    Reviewed-by: default avatarTom Rini <trini@konsulko.com>