Skip to content

Introduce LockUntilReleaseRRArbiter - #5525

Open
dennisgnad wants to merge 1 commit into
chipsalliance:mainfrom
Aurora7913:introduce-new-LockUntilReleaseRRArbiter
Open

dennisgnad wants to merge 1 commit into
chipsalliance:mainfrom
Aurora7913:introduce-new-LockUntilReleaseRRArbiter

Conversation

@dennisgnad

Copy link
Copy Markdown

Summary

This PR adds a LockUntilReleaseRRArbiter which is a locking round-robin arbiter that keeps the lock until a release signal allows another producer again.

Use cases are for instance networks or streams in which a packet is transported over multiple clock cycles that have a start and end delimiter, and interleaving of the data with others is not allowed. In such a case, the end can be connected to the release signal of the LockUntilReleaseRRArbiter.

Release Notes

This arbiter handles a gap in implementation of the current LockingArbiterLike-arbiters, which only work on a fixed clock cycle count. The newly introduced arbiter is instead controlled by an external signal instead of just a fixed count.

Development notes

  • AI tool(s) used: CoPilot Auto mode
  • Merge strategy (defaults to squash): squash
  • Milestone: -

I am a colleague of @maartenboersma and he suggested we could upstream this module, too. The question is, do we still need to provide tests of some sort? Other Chisel arbiters do not have them. Let me know what you still need for this PR, thanks!

@linux-foundation-easycla

linux-foundation-easycla Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: dennisgnad / name: Dennis Gnad (8dea575)

This branch has not been deployed

No deployments
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