diff options
| author | Suman Anna <s-anna@ti.com> | 2020-03-10 18:34:54 -0500 |
|---|---|---|
| committer | Lokesh Vutla <lokeshvutla@ti.com> | 2020-03-16 12:33:03 +0530 |
| commit | 0438a0a181675cb5d149184d8a6e50678cbc6d15 (patch) | |
| tree | 76b3eb86b23d453d100a308c028733386c333760 /drivers/remoteproc/ti_k3_r5f_rproc.c | |
| parent | 42005817ee70059c041884c5ce3ff69e1da13e95 (diff) | |
| download | u-boot-0438a0a181675cb5d149184d8a6e50678cbc6d15.zip u-boot-0438a0a181675cb5d149184d8a6e50678cbc6d15.tar.gz u-boot-0438a0a181675cb5d149184d8a6e50678cbc6d15.tar.bz2 | |
remoteproc: k3-r5: Fix rproc init failure for Main R5FSS0
The Main R5FSS0 cluster is also enabled to probe the R5F remoteproc
driver within R5 SPL for booting the Core0 very early. This results
in a ti_sci_power_domain_on failure during the probe from the A72
U-Boot when "rproc init" is executed at U-Boot prompt, and doesn't
enumerate all the rproc devices.
Fix this by suppressing the power_domain_on altogether using the
flag DM_FLAG_DEFAULT_PD_CTRL_OFF added in commit af94ad418dc7
("dm: core: Allow for not controlling the power-domain by DM framework").
Fixes: fac6aa817a09 ("configs: j721e_evm_r5: Enable R5F remoteproc support")
Signed-off-by: Suman Anna <s-anna@ti.com>
Diffstat (limited to 'drivers/remoteproc/ti_k3_r5f_rproc.c')
| -rw-r--r-- | drivers/remoteproc/ti_k3_r5f_rproc.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/remoteproc/ti_k3_r5f_rproc.c b/drivers/remoteproc/ti_k3_r5f_rproc.c index ea56689..2e2665f 100644 --- a/drivers/remoteproc/ti_k3_r5f_rproc.c +++ b/drivers/remoteproc/ti_k3_r5f_rproc.c @@ -816,4 +816,5 @@ U_BOOT_DRIVER(k3_r5fss) = { .id = UCLASS_MISC, .probe = k3_r5f_cluster_probe, .priv_auto_alloc_size = sizeof(struct k3_r5f_cluster), + .flags = DM_FLAG_DEFAULT_PD_CTRL_OFF, }; |