[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <893c8446-5c4b-0e16-6979-632a20c8a201@linaro.org>
Date: Tue, 13 Sep 2022 12:48:52 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
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 13/09/2022 12:21, 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].
Missing devicetree list (so no testing), missing bindings. Please follow
Linux process, run checkpatch and CC necessary people an dlists pointed
out by get_maintainers.pl.
Best regards,
Krzysztof
Powered by blists - more mailing lists