Searched hist:"20 af3c0a0034b885cd269cb7abdc2d933d82a723" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/drivers/core/ |
| H A D | uclass.c | 20af3c0a0034b885cd269cb7abdc2d933d82a723 Tue Jan 05 16:30:59 UTC 2016 Simon Glass <sjg@chromium.org> dm: core: Call uclass post_bind() after the driver's bind() method
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: Simon Glass <sjg@chromium.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|
| H A D | device.c | 20af3c0a0034b885cd269cb7abdc2d933d82a723 Tue Jan 05 16:30:59 UTC 2016 Simon Glass <sjg@chromium.org> dm: core: Call uclass post_bind() after the driver's bind() method
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: Simon Glass <sjg@chromium.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
|