MagTag SSD1680 contrast fix (FPC-7519rev.b only) - backport to 10.2.x#11000
Merged
Merged
Conversation
Collaborator
|
Turns out this is missing some code. Another PR is forthcoming. |
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
3 participants
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.
Backport of #10992 to the 10.2.x stable branch.
MagTag units with the SSD1680 - FPC-7519rev.b display panel (User ID byte
0xca) show bold, blurry text with the default firmware. This fix detects the panel by its User ID and applies a separate start sequence with the correct VCOM voltage (0x14= -1.0V) read directly from the panel's OTP register. All other MagTag panels are unaffected.Changes vs 10.2.x baseline:
ssd1680_vcom14_display_start_sequencewithVCOM=0x14for FPC-7519rev.bDISPLAY_SSD1680_COLSTART_8_VCOM14enum variantdetect_display_type(): addcase 0xcareturning the new variant (not present at all in 10.2.x)board_init(): select the correct start sequence based on detected panelForum thread