Messages in this thread | | | Subject | Re: [RESEND PATCH v3 11/11] clk: stm32mp1: new compatible for secure RCC support | From | Marek Vasut <> | Date | Thu, 17 Jun 2021 08:46:11 +0200 |
| |
On 6/17/21 7:18 AM, gabriel.fernandez@foss.st.com wrote: > From: Gabriel Fernandez <gabriel.fernandez@foss.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.
Should this really be a new compatible string or rather a DT property ? I think the later, since this is the same clock IP, only operating in different "mode" , no ?
| |