On 30/10/2019 02:48, Simon Glass wrote:
Hi Jean-Jacques,
On Wed, 2 Oct 2019 at 06:47, Jean-Jacques Hiblot <jjhib...@ti.com> wrote:
This will probe the multiplexer devices that have a "u-boot,mux-autoprobe"
property. As a consequence they will be put in their idle state.
Signed-off-by: Jean-Jacques Hiblot <jjhib...@ti.com>
---
common/board_r.c | 2 ++
1 file changed, 2 insertions(+)
I worry this should happen later, or lazily, since at present we don't
actually probe any devices at this point, right?
It has to be done early to make sure that the platform is in the right
state before most of the drivers are initialized. Some devices may rely
on it without knowing it. In this way, it is similar to the gpio-hog
mechanism.
Now, I have no strong opinion on when this should really take place.
Only it has to be after dm is initialized. Maybe it could be inserted in
init_sequence_r, after board_init() ?
It should probably be before the serial port is used, just in case
someone multiplexed the serial port of the console.
JJ
Regards,
Simon
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
