u-boot.git/drivers/remoteproc, branch v2021.01

remoteproc: stm32: update error management in stm32_copro_start

2020-11-25T10:32:31Z

The coprocessor is running as soon as the hold boot is de-asserted. So indicate this running state and save the resource table even if the protective assert, to avoid autonomous reboot, is failed. This error case should never occurs. Cc: Fabien DESSENNE Cc: Arnaud POULIQUEN Signed-off-by: Patrick Delaunay Reviewed-by: Patrice Chotard

remoteproc: stm32: use reset for hold boot

2020-11-25T10:32:31Z

Use the reset function to handle the hold boot bit in RCC with device tree handle with MCU_HOLD_BOOT identifier. This generic reset allows to remove the two specific properties: - st,syscfg-holdboot - st,syscfg-tz This patch prepares alignment with kernel device tree. Signed-off-by: Patrick Delaunay Cc: Fabien DESSENNE Cc: Arnaud POULIQUEN Reviewed-by: Patrice Chotard

remoteproc: k3: Fix not calling dev_xxx with a device

2020-09-30T12:53:42Z

Pass a device to functions which log with one. Signed-off-by: Sean Anderson Tested-by: Patrick Delaunay

remoteproc: k3-r5: Fix not calling dev_xxx with a device

2020-09-30T12:53:40Z

Usually we can get a device from the current core, but some dev_dbg calls have been converted to debug, since we are called on a cluster. Signed-off-by: Sean Anderson Tested-by: Patrick Delaunay

remoteproc: Remove unused function rproc_elf_sanity_check

2020-09-30T12:53:38Z

This function is never used anywhere, and it also tries to log with a nonexistant device. Signed-off-by: Sean Anderson Tested-by: Patrick Delaunay

remoteproc: k3-r5: Add support for J7200 R5Fs

2020-09-15T13:21:53Z

The K3 J7200 SoC family has a revised R5F sub-system and contains a subset of the R5F clusters present on J721E SoCs. The integration of these clusters is very much similar to J721E SoCs otherwise. The revised IP has the following two new features: 1. TCMs are auto-initialized during module power-up, and the behavior is programmable through a MMR bit controlled by System Firmware. 2. The LockStep-mode allows the Core1 TCMs to be combined with the Core0 TCMs effectively doubling the amount of TCMs available. The LockStep-mode on previous SoCs could only use the Core0 TCMs. This combined TCMs appear contiguous at the respective Core0 TCM addresses. Add the support to these clusters in the K3 R5F remoteproc driver using J7200 specific compatibles and revised logic accounting for the above IP features/differences. Signed-off-by: Suman Anna

common: Drop log.h from common header

2020-05-19T01:19:18Z

Move this header out of the common header. Signed-off-by: Simon Glass

common: Drop net.h from common header

2020-05-18T21:33:31Z

Move this header out of the common header. Network support is used in quite a few places but it still does not warrant blanket inclusion. Note that this net.h header itself has quite a lot in it. It could be split into the driver-mode support, functions, structures, checksumming, etc. Signed-off-by: Simon Glass

remoteproc: k3-r5: Fix rproc init failure on Split-mode _only_ devices

2020-03-16T07:03:19Z

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 Signed-off-by: Andreas Dannenberg Signed-off-by: Lokesh Vutla

remoteproc: k3-r5: Fix rproc init failure for Main R5FSS0

2020-03-16T07:03:03Z

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