[U-Boot] [PATCH 03/18] dm: core: Call uclass post_bind() after the driver's bind() method

Simon Glass sjg at chromium.org
Sat Jan 16 02:26:27 CET 2016


On 13 January 2016 at 14:55, Tom Rini <trini at konsulko.com> wrote:
> On Tue, Jan 05, 2016 at 09:30:59AM -0700, Simon Glass wrote:
>
>> 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 at chromium.org>
>
> Reviewed-by: Tom Rini <trini at konsulko.com>
>
> --
> Tom

Applied to u-boot-dm


More information about the U-Boot mailing list