[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <162484417735.3259633.16206197575374461808@swboyd.mtv.corp.google.com>
Date: Sun, 27 Jun 2021 18:36:17 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Alexandre Torgue <alexandre.torgue@...s.st.com>,
Etienne Carriere <etienne.carriere@...s.st.com>,
Gabriel Fernandez <gabriel.fernandez@...s.st.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Michael Turquette <mturquette@...libre.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Rob Herring <robh+dt@...nel.org>, marex@...x.de
Cc: linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH v3 11/11] clk: stm32mp1: new compatible for secure RCC support
Quoting gabriel.fernandez@...s.st.com (2021-06-16 22:18:14)
> From: Gabriel Fernandez <gabriel.fernandez@...s.st.com>
>
> Platform STM32MP1 can be used in configuration where some clock
> resources cannot be accessed by Linux kernel when executing in non-secure
> state of the CPU(s).
> In such configuration, the RCC clock driver must not register clocks
> it cannot access.
> They are expected to be registered from another clock driver such
> as the SCMI clock driver.
> This change uses specific compatible string "st,stm32mp1-rcc-secure"
> to specify RCC clock driver configuration where RCC is secure.
>
> Signed-off-by: Etienne Carriere <etienne.carriere@...s.st.com>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@...s.st.com>
> ---
Applied to clk-next
Powered by blists - more mailing lists