alexei.dolgolyov
d1f621f0b4
Lint & Test / test (push) Successful in 10s
DDC/CI writes are fire-and-forget at the protocol level: a successful send
does not mean the monitor honored the value. Many monitors (LG ultrawides
in particular) silently drop writes for VCP codes whose registers exist
but whose feature isn't really implemented in firmware.
- New _verify_after_set helper polls readback after every DDC/CI write and
reports {success: false} when the monitor didn't apply the value. Wired
into set_contrast, set_input_source, set_color_preset, set_picture_mode.
Input source uses a longer settle window since switching can briefly
disrupt the DDC/CI link.
- Picture mode (VCP 0xDC) now requires the capability string to declare
supported codes under cmds[0xDC]. Without that declaration we treat the
feature as unsupported even when reads succeed - the LG case where reads
return a stuck value and every write is silently ignored.