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@chromium.org
Reviewed-by: Tom Rini trini@konsulko.com