[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221005082348.v43xbjrhbdlbaohv@pengutronix.de>
Date: Wed, 5 Oct 2022 10:23:48 +0200
From: Marco Felsch <m.felsch@...gutronix.de>
To: 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: Peng Fan <peng.fan@....com>, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-imx@....com
Subject: Re: [RFC PATCH 0/2] Propose critical clocks
Hi Stephen, Michael,
I know it is a busy time right now, but maybe you have a few minutes for
this RFC. I know it is incomplete, but the interessting part is there
and it would fix a real issue we encountered on the imx8mm-evk's.
Regards,
Marco
On 22-09-13, 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].
>
> [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(+)
>
> --
> 2.30.2
>
>
>
Powered by blists - more mailing lists