This repository was archived by the owner on Nov 8, 2026. It is now read-only.
Repository navigation
Compositor: faster DRM hotplug (250 ms to 40 ms debounce) + dock latency breakdown - #388
Merged
Merged
Conversation
Journal timing of eight WD22TB4 plug cycles on the J314S shows the DCP driver sends its connector uevents ~9 ms apart with modes already populated, so the 250 ms wait was pure latency on connect and disconnect. The +1 s follow-up reconcile still covers late-settling connectors. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Why
Of ~4.5 s from partner attach to a mapped output, the compositor only owns ~0.5 s: a 250 ms debounce plus a ~245 ms synchronous DCP modeset. The DCP driver emits its connector uevents ~9 ms apart with modes already populated, so the debounce was pure latency on connect and disconnect. The +1 s follow-up reconcile is unchanged.
The other ~4 s is below the compositor (ACIO firmware AT-register timeout 2.36 s, TB enumeration, boltd authorization before the DP tunnel); see the doc.
Verified
🤖 Generated with Claude Code