On Thu, Mar 19, 2026 at 06:50:52AM +0100, Vyacheslav Yurkov wrote: > On 18.03.2026 23:55, Rob Herring wrote: > > On Wed, Mar 18, 2026 at 05:43:40PM +0000, Vyacheslav Yurkov wrote: > > > Describe device tree binding for virtual clock controller guard. > > No idea what this means. Please explain how I would identify this h/w. > > > > We generally don't do bindings for virtual devices and we don't do > > single clock bindings (other than some we are stuck with). > > > > 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. > > So in essence it's like a helper driver to simplify consumers probe > procedure. Does it make sense? If you don't do bindings for virtual HW, how > else would you approach this?