Re: [PATCH 2/2] dt-bindings: Add clock guard DT description
From: Vyacheslav Yurkov
Date: Mon Mar 23 2026 - 09:59:55 EST
On 19.03.2026 17:50, Conor Dooley wrote:
It partially covers the similar use case, but differs in the sense that gpio-gate-clock controls the clock via GPIO (enable/disable), the clock-controller-guard gets the GPIO status signals whether the clock _was_ enabled externally because a CPU has no direct access to the clock. So perhaps the terminology I came up with is not so self-explanatory, that's why I posted it for review and other opinions.I described a use case in my cover letter (PATCH 0). Perhaps our approach to
tackle the issue is not correct in the first place. The term "virtual clock
controller guard" is something we named it, but it's literally just a clock
provider which combines several other clocks and input GPIO signals in order
for the consumers to check whether they are allowed to probe already or have
to wait until the input clocks are enabled.
Can you explain how this is different to gpio-gate-clock? AFAICT, you're
trying to support clocks that are enabled by a gpio, and that's what it
is for.