[PATCH] remoteproc: k3-r5: Fix rproc init failure on Split-mode _only_ devices
lokeshvutla at ti.com
Mon Mar 16 16:38:42 CET 2020
On 11/03/20 6:54 AM, Suman Anna wrote:
> The R5F subsystem/cluster on K3 SoCs can support both LockStep and
> Split-modes (superset) or just Split-mode depending on an eFUSE
> capability register. The LockStep configuration bit is Read-only
> though on Split-mode _only_ devices and as such the System Firmware
> does not allow the LockStep mode bit to be configured on such devices.
> The current logic in k3_r5f_rproc_configure() fails on Split-mode
> devices because of this unconditional programming of the LockStep
> mode bit, and results in the probe failure shown during the
> "rproc init" step at U-Boot prompt.
> Fix this by limiting the LockStep mode bit clear configuration only on
> devices supporting both LockStep/Split-modes.
> Fixes: 4c850356a83f ("remoteproc: Introduce K3 remoteproc driver for R5F subsystem")
> Signed-off-by: Suman Anna <s-anna at ti.com>
> Signed-off-by: Andreas Dannenberg <dannenberg at ti.com>
> Signed-off-by: Lokesh Vutla <lokeshvutla at ti.com>
> Hi Lokesh,
> Verified the behavior on top of the ti/next branch on a custom
> board with the Split-mode only SoC.
Applied to u-boot-ti/next
Thanks and regards,
More information about the U-Boot