Skip to content

feat(ccu): add direct signal wait backend - #77

Draft
Kur0x wants to merge 2 commits into
codex/ccu-stack-05-backendfrom
codex/ccu-stack-06-signal-wait
Draft

feat(ccu): add direct signal wait backend#77
Kur0x wants to merge 2 commits into
codex/ccu-stack-05-backendfrom
codex/ccu-stack-06-signal-wait

Conversation

@Kur0x

@Kur0x Kur0x commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • harden opt-in direct runtime lifecycle and graceful initialization fallback
  • add direct signal/wait program generation and backend preparation/submission
  • preserve lower-layer ownership and repeated-launch cleanup

Stack

6 of 9. Depends on codex/ccu-stack-05-backend.

Validation

  • git diff --check
  • signal/wait, backend, orchestrator, smoke-source, runner, driver, and allocator tests
  • 139 of 142 local tests passed; 3 Linux dynamic-loader tests are unavailable on macOS and remain enabled for CI

Scope

No fresh NPU hardware validation was run from this macOS host.

}
program->clear();

if (spec.role == TileXRCcuSignalWaitProgramRole::Wait) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please validate spec.role before selecting the program shape. Any enum value outside Signal, Wait, and SignalAndWait currently falls through as Signal and returns success, potentially posting a remote notification for a malformed request.

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.

2 participants