Messages in this thread | | | Date | Tue, 13 Sep 2022 13:51:23 +0200 | From | Marco Felsch <> | Subject | Re: [RFC PATCH 0/2] Propose critical clocks |
| |
On 22-09-13, Krzysztof Kozlowski wrote: > 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.
I just pushd the _proposal_ as reaction of adding a NXP specific binding. If the clk maintainer(s) would agree to this this proposal I would update the patchset with bindings and _all_ mail-addresses.
Regards, Marco
| |