From: <gabriel.fernandez@foss.st.com> To: Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>, Maxime Coquelin <mcoquelin.stm32@gmail.com>, Alexandre Torgue <alexandre.torgue@st.com>, Philipp Zabel <p.zabel@pengutronix.de>, Etienne Carriere <etienne.carriere@st.com>, Gabriel Fernandez <gabriel.fernandez@foss.st.com>, <marex@denx.de> Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH v3 00/11] Introduce STM32MP1 RCC in secured mode Date: Mon, 19 Apr 2021 11:38:41 +0200 [thread overview] Message-ID: <20210419093852.14978-1-gabriel.fernandez@foss.st.com> (raw) From: Gabriel Fernandez <gabriel.fernandez@foss.st.com> Platform STM32MP1 can be used in configuration where some clocks and IP resets can relate as secure resources. These resources are moved from a RCC clock/reset handle to a SCMI clock/reset_domain handle. The RCC clock driver is now dependent of the SCMI driver, then we have to manage now the probe defering. v2 -> v3: - use determine_rate op instead of round_rate for ck_rtc - remove DT patches from patchset to keek Kernel device tree as there are in basic boot. We will applied scmi clock phandle thanks dtbo in U-boot. v1 -> v2: - fix yamllint warnings. Gabriel Fernandez (11): clk: stm32mp1: merge 'clk-hsi-div' and 'ck_hsi' into one clock clk: stm32mp1: merge 'ck_hse_rtc' and 'ck_rtc' into one clock clk: stm32mp1: remove intermediate pll clocks clk: stm32mp1: convert to module driver clk: stm32mp1: move RCC reset controller into RCC clock driver reset: stm32mp1: remove stm32mp1 reset dt-bindings: clock: add IDs for SCMI clocks on stm32mp15 dt-bindings: reset: add IDs for SCMI reset domains on stm32mp15 dt-bindings: reset: add MCU HOLD BOOT ID for SCMI reset domains on stm32mp15 dt-bindings: clock: stm32mp1 new compatible for secure rcc clk: stm32mp1: new compatible for secure RCC support .../bindings/clock/st,stm32mp1-rcc.yaml | 6 +- drivers/clk/Kconfig | 10 + drivers/clk/clk-stm32mp1.c | 500 +++++++++++++++--- drivers/reset/Kconfig | 6 - drivers/reset/Makefile | 1 - drivers/reset/reset-stm32mp1.c | 115 ---- include/dt-bindings/clock/stm32mp1-clks.h | 27 + include/dt-bindings/reset/stm32mp1-resets.h | 15 + 8 files changed, 469 insertions(+), 211 deletions(-) delete mode 100644 drivers/reset/reset-stm32mp1.c -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: <gabriel.fernandez@foss.st.com> To: Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>, Maxime Coquelin <mcoquelin.stm32@gmail.com>, Alexandre Torgue <alexandre.torgue@st.com>, Philipp Zabel <p.zabel@pengutronix.de>, Etienne Carriere <etienne.carriere@st.com>, Gabriel Fernandez <gabriel.fernandez@foss.st.com>, <marex@denx.de> Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH v3 00/11] Introduce STM32MP1 RCC in secured mode Date: Mon, 19 Apr 2021 11:38:41 +0200 [thread overview] Message-ID: <20210419093852.14978-1-gabriel.fernandez@foss.st.com> (raw) From: Gabriel Fernandez <gabriel.fernandez@foss.st.com> Platform STM32MP1 can be used in configuration where some clocks and IP resets can relate as secure resources. These resources are moved from a RCC clock/reset handle to a SCMI clock/reset_domain handle. The RCC clock driver is now dependent of the SCMI driver, then we have to manage now the probe defering. v2 -> v3: - use determine_rate op instead of round_rate for ck_rtc - remove DT patches from patchset to keek Kernel device tree as there are in basic boot. We will applied scmi clock phandle thanks dtbo in U-boot. v1 -> v2: - fix yamllint warnings. Gabriel Fernandez (11): clk: stm32mp1: merge 'clk-hsi-div' and 'ck_hsi' into one clock clk: stm32mp1: merge 'ck_hse_rtc' and 'ck_rtc' into one clock clk: stm32mp1: remove intermediate pll clocks clk: stm32mp1: convert to module driver clk: stm32mp1: move RCC reset controller into RCC clock driver reset: stm32mp1: remove stm32mp1 reset dt-bindings: clock: add IDs for SCMI clocks on stm32mp15 dt-bindings: reset: add IDs for SCMI reset domains on stm32mp15 dt-bindings: reset: add MCU HOLD BOOT ID for SCMI reset domains on stm32mp15 dt-bindings: clock: stm32mp1 new compatible for secure rcc clk: stm32mp1: new compatible for secure RCC support .../bindings/clock/st,stm32mp1-rcc.yaml | 6 +- drivers/clk/Kconfig | 10 + drivers/clk/clk-stm32mp1.c | 500 +++++++++++++++--- drivers/reset/Kconfig | 6 - drivers/reset/Makefile | 1 - drivers/reset/reset-stm32mp1.c | 115 ---- include/dt-bindings/clock/stm32mp1-clks.h | 27 + include/dt-bindings/reset/stm32mp1-resets.h | 15 + 8 files changed, 469 insertions(+), 211 deletions(-) delete mode 100644 drivers/reset/reset-stm32mp1.c -- 2.17.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:[~2021-04-19 9:39 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-19 9:38 gabriel.fernandez [this message] 2021-04-19 9:38 ` [PATCH v3 00/11] Introduce STM32MP1 RCC in secured mode gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 01/11] clk: stm32mp1: merge 'clk-hsi-div' and 'ck_hsi' into one clock gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 02/11] clk: stm32mp1: merge 'ck_hse_rtc' and 'ck_rtc' " gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 03/11] clk: stm32mp1: remove intermediate pll clocks gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 04/11] clk: stm32mp1: convert to module driver gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 05/11] clk: stm32mp1: move RCC reset controller into RCC clock driver gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 06/11] reset: stm32mp1: remove stm32mp1 reset gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 07/11] dt-bindings: clock: add IDs for SCMI clocks on stm32mp15 gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 08/11] dt-bindings: reset: add IDs for SCMI reset domains " gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 09/11] dt-bindings: reset: add MCU HOLD BOOT ID " gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-19 9:38 ` [PATCH v3 10/11] dt-bindings: clock: stm32mp1 new compatible for secure rcc gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez 2021-04-20 16:25 ` Rob Herring 2021-04-20 16:25 ` Rob Herring 2021-04-20 18:30 ` Marek Vasut 2021-04-20 18:30 ` Marek Vasut 2021-04-19 9:38 ` [PATCH v3 11/11] clk: stm32mp1: new compatible for secure RCC support gabriel.fernandez 2021-04-19 9:38 ` gabriel.fernandez
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=20210419093852.14978-1-gabriel.fernandez@foss.st.com \ --to=gabriel.fernandez@foss.st.com \ --cc=alexandre.torgue@st.com \ --cc=devicetree@vger.kernel.org \ --cc=etienne.carriere@st.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=marex@denx.de \ --cc=mcoquelin.stm32@gmail.com \ --cc=mturquette@baylibre.com \ --cc=p.zabel@pengutronix.de \ --cc=robh+dt@kernel.org \ --cc=sboyd@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.