[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e61d2168-9114-6f95-2607-a553d1046caa@linaro.org>
Date: Sun, 14 May 2023 11:40:26 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Bjorn Andersson <andersson@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Alexandre Torgue <alexandre.torgue@...s.st.com>
Cc: devicetree@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org,
linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: remoteproc: st,stm32-rproc: Rework
reset declarations
On 12/05/2023 11:39, Arnaud Pouliquen wrote:
> 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.
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Best regards,
Krzysztof
Powered by blists - more mailing lists