Skip to content

feat: preserve publication outcome across doorbell failure - #2

Draft
sanchuanhehe wants to merge 2 commits into
feat/ws53-coex-quiescent-reclaimfrom
feat/ws53-coex-notification-result
Draft

sanchuanhehe wants to merge 2 commits into
feat/ws53-coex-quiescent-reclaimfrom
feat/ws53-coex-notification-result

Conversation

@sanchuanhehe

Copy link
Copy Markdown
Contributor

A doorbell operation can fail after a message has already been published. Expose a publish-then-notify helper that distinguishes notification failure from publication failure, so callers do not blindly resend a published frame.

The platform still owns notification resources, cache ordering, peer ACK/drain/recheck, and recovery of indeterminate publication; a successful or pending doorbell does not prove peer delivery. No ISR or async implementation is claimed.

Validation: 32 host tests including a synthetic SDK SPSC peer and indeterminate publication; host and RISC-V Clippy. Real firmware, QEMU doorbell integration, and silicon behavior remain unqualified.

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