On Mon, 07 Apr 2025 07:15:54 -0500, Nishanth Menon wrote:
> When FIT image with multiple dtbs are involved for R5 boot process,
> R5 SPL starts off with the first instance of dtb to probe the
> eeprom, then once we have identified the type of board, invocation
> of setup_multi_dtb_fit will replace the gd->fdt_blob with the proper
> board dtb match. However, when we do this, two things happen:
>
> a) Prior to the invocation of setup_multi_dtb_fit, as part of the eeprom
> discovery process, i2c controller device is already probed and marked
> as exclusive with the match of the very first tisci match (from the
> original boot dtb). This list is stored in the info->dev_list of the
> first probe.
> b) When the second dtb is loaded, tisci is probed again (since this is a
> new node) and the new info->dev_list is empty.
>
> [...]
Applied to u-boot/master, thanks!
[1/1] firmware: ti_sci: Scan all device instances when releasing exclusive
devices
commit: cce329426f61ad9c42775128d2c995ccd2ebdcfc
--
Tom
