[Bug] `OS_DETECTION_KEYBOARD_RESET` breaks USB suspend

[tsipinakis]

Describe the Bug

With a keyboard configured with OS_DETECTION_KEYBOARD_RESET, when connecting the keyboard through a KVM and powering off the main computer the keyboard resets as the KVM keeps it powered and detects OS_UNKNOWN (correctly) but fails to suspend. With the rest option disabled USB suspend happens correctly, but OS detection is then broken as it's stuck on the first identified OS.

Keyboard Used

Splitkb/helix

Link to product page (if applicable)

No response

Operating System

Linux

qmk doctor Output

Ψ Detected Linux (Debian GNU/Linux trixie/sid).
Ψ Userspace enabled: False
Ψ Git branch: master
Ψ Repo version: 0.27.9

Is AutoHotKey / Karabiner installed

• AutoHotKey (Windows)
• Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

[drashna]

The issue isn't the config option. In fact, it's doing exactly what it's being told. The issue is that the kvm isn't properly relaying the USB status.

If you are plugging into a USB hub or derectly into the PC, I highly suspect that this issue will immediately go away.

And if you're plugging into a decend KVM, this won't happen either. (source, my KVM doesn't trigger this behavior, and I do have OS_DETECTION_KEYBOARD_RESET enabled, explicitly to reset on kvm switch).