Conversation
Reapply DSC when a capable DisplayPort sink rejoins an attached SST group using single or dual DSC, restoring decompression and tracking.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reinserting an SST sink into an attached group restored membership without reapplying DSC, so a sink that had lost its enable state could remain blank.
Reapplied DSC through
setDeviceDscState()for capable DisplayPort sinks in attached SST groups using single or dual DSC, restoring sink decompression and driver tracking.FEC handling remained unchanged: the captured wakes requested skipping redundant link training, but the existing
train()path could still configure FEC. Sink FEC state was not separately measured.Regression tests