[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220816150201.GS2387@pengutronix.de>
Date: Tue, 16 Aug 2022 17:02:01 +0200
From: Sascha Hauer <s.hauer@...gutronix.de>
To: "Peng Fan (OSS)" <peng.fan@....nxp.com>
Cc: abelvesa@...nel.org, abel.vesa@...aro.org, mturquette@...libre.com,
sboyd@...nel.org, shawnguo@...nel.org, kernel@...gutronix.de,
festevam@...il.com, linux-imx@....com, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Peng Fan <peng.fan@....com>
Subject: Re: [PATCH V2] clk: imx: support protected-clocks
On Tue, Aug 16, 2022 at 09:03:27PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@....com>
>
> For the clocks listed in protected-clocks, enable them to avoid
> Linux disable them. This will benifit root Linux and inmate cell run
> on top of Jailhouse hypervisor, and benifit the other case(
> A53 Linux run together with M7 RTOS).
>
> Signed-off-by: Peng Fan <peng.fan@....com>
> ---
>
> V2:
> Per Sascha, use common protected-clocks property.
See my mail to v1. I did not request that you should use the
protected-clocks property:
> There were cases when a property first started with a "soc," prefix and
> later when people realized that it could be useful for other
> drivers/SoCs as well, the prefix was removed. With that in mind I
> would expect that a "fsl,protected-clocks" property behaves the same
> as a "protected-clocks" property without the prefix.
>
> If it doesn't please pick a different name. I didn't want to suggest
> to just drop the "fsl," prefix and to use the generic property name
> when the properties have a different meaning.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists