[PATCH] dm: core: Read parent ofdata before children

sjg at google.com sjg at google.com
Fri Apr 10 21:31:00 CEST 2020

Hi Tom,

On Mon, 6 Apr 2020 at 06:17, Tom Rini <trini at konsulko.com> wrote:
> On Sun, Apr 05, 2020 at 03:38:19PM -0600, Simon Glass wrote:
> > At present a device can read its ofdata before its parent has done the
> > same. This can cause problems in the case where the parent has a 'ranges'
> > property, thus affecting the operation of dev_read_addr(), for example.
> >
> > We already probe parent devices before children so it does not seem to be
> > a large step to do the same with ofdata.
> >
> > Make the change and update the documentation in this area.
> >
> > Signed-off-by: Simon Glass <sjg at chromium.org>
> Is this intended for the current release, or part of the changes you had
> been thinking about for the next release?  Also, with this change should
> we undo other changes that had adapted to 82de42fa1468 ?  Thanks!

I am not keen on adding this into the current release as it might
break other things. I have been trying to think of what problems it
could cause, but it is hard to be sure.

We can bring it in as soon as the merge window opens and then undo
those changes that are not needed.


Applied to u-boot-dm/next, thanks!

More information about the U-Boot mailing list