Currently the driver relies on bootph flag to probe it during PRE_RELOC stage but with the upcoming cleanup of v6.13, we don't have the bootph property in the parent nodes anymore and ti_sci driver being one of the parent nodes required during SPL stage would end up hampering the probe model [0].
Add DM_FLAG_PRE_RELOC to ti_sci driver for mitigating this issue. [0]: https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/21 Suggested-by: Vignesh Raghavendra <vigne...@ti.com> Signed-off-by: Manorit Chawdhry <m-chawd...@ti.com> --- Test logs with current DT: https://gist.github.com/manorit2001/b28bebd8229818412ff74e40d4a53f71 Test logs with 6.13-rc3 DT: https://gist.github.com/manorit2001/b91691b59581d445c301e2608ce5931a --- drivers/firmware/ti_sci.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/firmware/ti_sci.c b/drivers/firmware/ti_sci.c index 719cfa771b4198159a305a08a044c7a8aaf7a14f..190a1e3f5fc3713464b0cbf3ae8c35e3f185a353 100644 --- a/drivers/firmware/ti_sci.c +++ b/drivers/firmware/ti_sci.c @@ -3077,6 +3077,7 @@ U_BOOT_DRIVER(ti_sci) = { .of_match = ti_sci_ids, .probe = ti_sci_probe, .priv_auto = sizeof(struct ti_sci_info), + .flags = DM_FLAG_PRE_RELOC, }; #if IS_ENABLED(CONFIG_K3_DM_FW) --- base-commit: 9bc62c980d418f0a67632ab29cd3501072cdb6f0 change-id: 20241216-b4-upstream-dm-pre-reloc-583134d2a340 Best regards, -- Manorit Chawdhry <m-chawd...@ti.com>
