From: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Bjorn Andersson <andersson@kernel.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Alexandre Torgue <alexandre.torgue@foss.st.com> Cc: <devicetree@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <linux-arm-kernel@lists.infradead.org>, <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Arnaud Pouliquen <arnaud.pouliquen@foss.st.com> Subject: [PATCH v2 0/4] stm32mp15: update remoteproc to support SCMI Device tree Date: Thu, 4 May 2023 11:46:37 +0200 [thread overview] Message-ID: <20230504094641.870378-1-arnaud.pouliquen@foss.st.com> (raw) Update vs V1[1]: --------------- - Keep compatibility with legacy DT by keeping support of st,syscfg-tz property - Add comments to explain the different configuration supported for the old boot [1]https://lore.kernel.org/lkml/DU0PR04MB941747DDF6FD2F157A24183288939@DU0PR04MB9417.eurprd04.prod.outlook.com/t/ Description: ----------- This series updates the stm32_rproc driver and associated DT node to support device tree configuration with and without SCMI server. The impact is mainly on the MCU hold boot management. Three configurations have to be supported: 1) Configuration without OP-TEE SCMI (legacy): Trusted context not activated - The MCU reset is controlled through the Linux RCC reset driver. - The MCU HOLD BOOT is controlled through The RCC sysconf. 2) Configuration with SCMI server: Trusted context activated - The MCU reset is controlled through the SCMI reset service. - The MCU HOLD BOOT is no more controlled through a SMC call service but through the SCMI reset service. 3) Configuration with OP-TEE SMC call (deprecated): Trusted context activated - The MCU reset is controlled through the Linux RCC reset driver. - The MCU HOLD BOOT is controlled through The SMC call. In consequence this series: - adds the use of the SCMI reset service to manage the MCU hold boot, - determines the configuration to use depending on the presence of the "reset-names" property if ( "reset-names" property contains "hold_boot") then use reset_control services else use regmap access based on "st,syscfg-holdboot" property. - set the DT st,syscfg-tz property as deprecated Arnaud Pouliquen (4): dt-bindings: remoteproc: st,stm32-rproc: Rework reset declarations remoteproc: stm32: Allow hold boot management by the SCMI reset controller ARM: dts: stm32: Update reset declarations ARM: dts: stm32: fix m4_rproc references to use scmi .../bindings/remoteproc/st,stm32-rproc.yaml | 42 ++++++++-- arch/arm/boot/dts/stm32mp151.dtsi | 2 +- arch/arm/boot/dts/stm32mp157a-dk1-scmi.dts | 6 +- arch/arm/boot/dts/stm32mp157c-dk2-scmi.dts | 6 +- arch/arm/boot/dts/stm32mp157c-ed1-scmi.dts | 6 +- arch/arm/boot/dts/stm32mp157c-ev1-scmi.dts | 6 +- drivers/remoteproc/stm32_rproc.c | 78 ++++++++++++++----- 7 files changed, 111 insertions(+), 35 deletions(-) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Bjorn Andersson <andersson@kernel.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Alexandre Torgue <alexandre.torgue@foss.st.com> Cc: <devicetree@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <linux-arm-kernel@lists.infradead.org>, <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Arnaud Pouliquen <arnaud.pouliquen@foss.st.com> Subject: [PATCH v2 0/4] stm32mp15: update remoteproc to support SCMI Device tree Date: Thu, 4 May 2023 11:46:37 +0200 [thread overview] Message-ID: <20230504094641.870378-1-arnaud.pouliquen@foss.st.com> (raw) Update vs V1[1]: --------------- - Keep compatibility with legacy DT by keeping support of st,syscfg-tz property - Add comments to explain the different configuration supported for the old boot [1]https://lore.kernel.org/lkml/DU0PR04MB941747DDF6FD2F157A24183288939@DU0PR04MB9417.eurprd04.prod.outlook.com/t/ Description: ----------- This series updates the stm32_rproc driver and associated DT node to support device tree configuration with and without SCMI server. The impact is mainly on the MCU hold boot management. Three configurations have to be supported: 1) Configuration without OP-TEE SCMI (legacy): Trusted context not activated - The MCU reset is controlled through the Linux RCC reset driver. - The MCU HOLD BOOT is controlled through The RCC sysconf. 2) Configuration with SCMI server: Trusted context activated - The MCU reset is controlled through the SCMI reset service. - The MCU HOLD BOOT is no more controlled through a SMC call service but through the SCMI reset service. 3) Configuration with OP-TEE SMC call (deprecated): Trusted context activated - The MCU reset is controlled through the Linux RCC reset driver. - The MCU HOLD BOOT is controlled through The SMC call. In consequence this series: - adds the use of the SCMI reset service to manage the MCU hold boot, - determines the configuration to use depending on the presence of the "reset-names" property if ( "reset-names" property contains "hold_boot") then use reset_control services else use regmap access based on "st,syscfg-holdboot" property. - set the DT st,syscfg-tz property as deprecated Arnaud Pouliquen (4): dt-bindings: remoteproc: st,stm32-rproc: Rework reset declarations remoteproc: stm32: Allow hold boot management by the SCMI reset controller ARM: dts: stm32: Update reset declarations ARM: dts: stm32: fix m4_rproc references to use scmi .../bindings/remoteproc/st,stm32-rproc.yaml | 42 ++++++++-- arch/arm/boot/dts/stm32mp151.dtsi | 2 +- arch/arm/boot/dts/stm32mp157a-dk1-scmi.dts | 6 +- arch/arm/boot/dts/stm32mp157c-dk2-scmi.dts | 6 +- arch/arm/boot/dts/stm32mp157c-ed1-scmi.dts | 6 +- arch/arm/boot/dts/stm32mp157c-ev1-scmi.dts | 6 +- drivers/remoteproc/stm32_rproc.c | 78 ++++++++++++++----- 7 files changed, 111 insertions(+), 35 deletions(-) -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-05-04 9:47 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-04 9:46 Arnaud Pouliquen [this message] 2023-05-04 9:46 ` [PATCH v2 0/4] stm32mp15: update remoteproc to support SCMI Device tree Arnaud Pouliquen 2023-05-04 9:46 ` [PATCH v2 1/4] dt-bindings: remoteproc: st,stm32-rproc: Rework reset declarations Arnaud Pouliquen 2023-05-04 9:46 ` Arnaud Pouliquen 2023-05-05 7:13 ` Krzysztof Kozlowski 2023-05-05 7:13 ` Krzysztof Kozlowski 2023-05-04 9:46 ` [PATCH v2 2/4] remoteproc: stm32: Allow hold boot management by the SCMI reset controller Arnaud Pouliquen 2023-05-04 9:46 ` Arnaud Pouliquen 2023-05-05 17:03 ` Mathieu Poirier 2023-05-05 17:03 ` Mathieu Poirier 2023-05-09 13:10 ` Arnaud POULIQUEN 2023-05-04 9:46 ` [PATCH v2 3/4] ARM: dts: stm32: Update reset declarations Arnaud Pouliquen 2023-05-04 9:46 ` Arnaud Pouliquen 2023-05-04 9:46 ` [PATCH v2 4/4] ARM: dts: stm32: fix m4_rproc references to use SCMI Arnaud Pouliquen 2023-05-04 9:46 ` Arnaud Pouliquen
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230504094641.870378-1-arnaud.pouliquen@foss.st.com \ --to=arnaud.pouliquen@foss.st.com \ --cc=alexandre.torgue@foss.st.com \ --cc=andersson@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=mathieu.poirier@linaro.org \ --cc=robh+dt@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.