summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorArnaud Pouliquen <arnaud.pouliquen@foss.st.com>2023-05-12 12:39:23 +0300
committerMathieu Poirier <mathieu.poirier@linaro.org>2023-05-15 20:21:06 +0300
commitef7129db96cb1ecf627ca82677f34ac3b37edab2 (patch)
treea72fc062bc4feed2524a762fffcd08af2a6b9667 /drivers
parent47f64e7ef95a58e5c56f2ec62cbadbe868661149 (diff)
downloadlinux-ef7129db96cb1ecf627ca82677f34ac3b37edab2.tar.xz
dt-bindings: remoteproc: st,stm32-rproc: Rework reset declarations
With the introduction of the SCMI (System Control and Management Interface), it is now possible to use the SCMI to handle the hold boot instead of a dedicated SMC call. As consequence two configurations are possible: - without SCMI server on OP-TEE: use the Linux rcc reset service and use syscon for the MCU hold boot - With SCMI server on OP-TEE: use the SCMI reset service for both the MCU reset and the MCU hold boot. This patch: - make optional and deprecated the use of the property st,syscfg-tz which was used to check if the trusted Zone was enable to use scm call, to manage the hold boot. The reset controller phandle is used instead to select the configurations. - make st,syscfg-holdboot optional - adds properties check on resets definitions. - adds an example of the SCMI reset service usage. Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/20230512093926.661509-2-arnaud.pouliquen@foss.st.com Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions