On Tue, 29 Sep 2026 13:18:40 +0000, [email protected] wrote: > Could this result in the vsync being permanently missed, causing the wait > to timeout?
Yes, the window is real; I did not hit it in 13 cycles, but nothing prevents it. v2 stopped only the slave interfaces up front, and v3 follows Dmitry's suggestion and disables the slave before the master, so no timing engine is stopped outside its own disable path: https://lore.kernel.org/all/[email protected]/ Thanks, Joonhoe
