drm: add support for generic color pipeline API #1309
Draft
Conversation
This file contains 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
emersion
force-pushed
the
color-pipeline
branch
3 times, most recently
from
13b477d
to
63e314f
Compare
|
Hrm, for libliftoff integration we'll probably want to disable the color pipeline, run libliftoff, then get back the plane picked by libliftoff and program the color pipeline for that plane before the final commit. Not great at all, but anything else is going to be pain... |
|
Neat, glad to see this getting somewhere. Yeah test commits are increasingly expensive with color stuff... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To be tested with https://gitlab.freedesktop.org/hwentland/linux/-/commits/color-pipeline-wip-1