On Mon Jan 19, 2026 at 1:54 PM CET, Daniel Almeida wrote: >> On 19 Jan 2026, at 09:35, Alice Ryhl <[email protected]> wrote: >> I think that if you still want an API where you just call enable/disable >> directly on it with no protection against unbalanced calls, then that >> should be the special API. Probably called RawClk and functions marked >> unsafe. Unbalanced calls seem really dangerous and use should not be >> encouraged.
+1; and unless there is a use-case that requires otherwise, it should not even be possible to do this at all -- at least for driver code. > I think we should discourage RawClk if at all possible. But if the consensus > is that we *really* need this easily-abused thing, I can provide a follow-up. I think we should only do this if there are use-case with no alternative, so far there haven't been any AFAIK.
