(We don't use the -dm mailing list...perhaps it should be deleted?)
On Wed, 27 Feb 2019 at 09:22, viktor babrian viktor.babrian@gmail.com wrote:
Hi,
as far as I understood, the pre-reloc device binding of drivers having DM_FLAG_PRE_RELOC flag set is only performed for top-level devices - at least that is what I experience. Is this intentional? What is the concept there? I am trying to use a spi slave display that is by default described as a node under root/soc/spiX. We have the device working under Linux. I understand these displays are not supported as is in u-boot so I ported some Linux code and made some minor mods in the video uclass. Still I do not have memory reserved for the frame-buffer and debugging shows that it is because bind() is not invoked pre-reloc. And it is not invoked because dm_extended_scan_fdt() parses top-level nodes only. I wonder if that pre-reloc scan is so for some purpose because a recursive scan would seemingly be justified in my case. (or am I just missing something?)
Any comments are welcome, Thanks, Viktor _______________________________________________ U-Boot-DM mailing list U-Boot-DM@lists.denx.de https://lists.denx.de/listinfo/u-boot-dm