DPTX: add 25ms delay to make 1st stage display init reliable #338
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
Signed-off-by: Janne Grunau <j@jannau.net>
Fixes display initialization from stage 1 m1n1. 20ms looked reliable on j473 but let's add 25% safety margin. Someone with more motivation (and HW serial) to do repeated `kmutil configure-boot ...` can try to minimize this and test on t602x. Signed-off-by: Janne Grunau <j@jannau.net>
jannau
force-pushed
the
dptx_1st_stage_delay
branch
from
68c05e6 to
2b942b3
Compare
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.
Fixes display initialization from stage 1 m1n1. 20ms looked reliable on
j473 but let's add 25% safety margin. Someone with more motivation (and
HW serial) to do repeated
kmutil configure-boot ...can try tominimize this and test on t602x
Also silence some afk/dptx printf() by converting them to dprintf().