[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30a8c599-583a-3eea-c7bf-04062c43b736@oss.nxp.com>
Date: Tue, 13 Sep 2022 20:24:47 +0800
From: Peng Fan <peng.fan@....nxp.com>
To: Marco Felsch <m.felsch@...gutronix.de>,
krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org,
abelvesa@...nel.org, abel.vesa@...aro.org, mturquette@...libre.com,
sboyd@...nel.org, shawnguo@...nel.org, s.hauer@...gutronix.de,
kernel@...gutronix.de, festevam@...il.com
Cc: linux-kernel@...r.kernel.org, Peng Fan <peng.fan@....com>,
linux-imx@....com, linux-arm-kernel@...ts.infradead.org,
linux-clk@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] Propose critical clocks
On 9/13/2022 6:21 PM, Marco Felsch wrote:
> Hi,
>
> this proposal is to mark clocks as critical. It is somehow inspired by
> the regulator-always-on property. Since sometimes we can end in circular
> dependcies if we wanna solve the dependcies for a specific clock
> provider.
>
> The property is generic so it can be used by every hw clock provider. So
> it can be seen as generic implementation to [1].
Thanks for working on a generic solution, I think your proposal could
also help [1] and try to resolve same issue as [2].
[1]
https://lore.kernel.org/all/CAJ+vNU1Za2CPGVX3q4HKufsxbL5zRrk1B5CWFpKritetrTs4dA@mail.gmail.com/
[2]
https://lore.kernel.org/all/20220517235919.200375-1-marex@denx.de/T/#m52d6d0831bf43d5f293e35cb27f3021f278d0564
Thanks,
Peng.
>
> [1] https://lore.kernel.org/linux-clk/20220913092136.1706263-1-peng.fan@oss.nxp.com/
>
> Marco Felsch (2):
> clk: add support for critical always-on clocks
> arm64: dts: imx8mm-evk: mark 32k pmic clock as always-on
>
> arch/arm64/boot/dts/freescale/imx8mm-evk.dtsi | 1 +
> drivers/clk/clk.c | 18 ++++++++++++++++++
> 2 files changed, 19 insertions(+)
>
Powered by blists - more mailing lists