psyqo: split GPU register setup into reinitialize()#2050
Open
nicolasnoble wants to merge 1 commit into
Open
Conversation
Factor the re-runnable part of initialize() - the display-mode, range and display-area register writes plus the derived width/height/refresh state - into a new reinitialize(), so the video mode can be reconfigured without re-installing the VBlank handler, DMA events and timers. initialize() keeps the one-time setup and calls reinitialize(). Behavior is unchanged: the register values and write order are identical; only the Timer1 (COUNTERS[1]) setup moves ahead of the register writes, which is independent. Co-authored-by: Elias Daler <eliasdaler@protonmail.com> Signed-off-by: Nicolas 'Pixel' Noble <nicolas@nobis-crew.org>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughA new ChangesGPU reinitialize refactor
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant Caller
participant GPU_initialize as GPU::initialize
participant GPU_reinitialize as GPU::reinitialize
Caller->>GPU_initialize: initialize(config)
GPU_initialize->>GPU_initialize: set COUNTERS[1].mode/value
GPU_initialize->>GPU_reinitialize: reinitialize(config)
GPU_reinitialize->>GPU_reinitialize: program GPU control registers
GPU_reinitialize->>GPU_reinitialize: derive display/interlace state
GPU_reinitialize-->>GPU_initialize: return
GPU_initialize->>GPU_initialize: continue VBlank/DMA setup
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Jul 8, 2026
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
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.
Factor the re-runnable part of initialize() - the display-mode, range and
display-area register writes plus the derived width/height/refresh state -
into a new reinitialize(), so the video mode can be reconfigured without
re-installing the VBlank handler, DMA events and timers. initialize() keeps
the one-time setup and calls reinitialize(). Behavior is unchanged: the
register values and write order are identical; only the Timer1 (COUNTERS[1])
setup moves ahead of the register writes, which is independent.