Skip to content

drm/asahi: g17: say what the stampless render retirement relies on - #569

Merged
DjDeveloperr merged 1 commit into
integration/aurorafrom
doc/g17-stampless-retirement
Oct 29, 2026
Merged

DjDeveloperr merged 1 commit into
integration/aurorafrom
doc/g17-stampless-retirement

Conversation

@DjDeveloperr

Copy link
Copy Markdown

Comment-only follow-up to #555, from chriskearney's question on omacom#264. The stampless retirement path has no post-maintenance evidence: whether the firmware completes the end-of-render maintenance before it advances the done cursors isn't known. The comments on STAMP_FALLBACK_NS and poll_stampless() now say that a group retired this way relies on the 50 ms bound, both for the fence and for the timestamps the host writes. No code change. asahi KUnit (minimal arm64 config): 188 tests, 186 pass, 2 skip.

A render group whose completion stamps stall retires on its pass record
after STAMP_FALLBACK_NS. The comment said the stamps follow the cache
maintenance after a pass, but not that this path has no such evidence:
whether the firmware completes the maintenance before it advances the
done cursors is not known. Say that a group retired this way relies on
the 50 ms bound for its counts, stores and exported timestamps to be
visible. Comment only.

Signed-off-by: DjDeveloperr <hey@djdev.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant