Add "out-of-band" signals to internal bus interface #1131
Merged
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.
The signals of the request bus are split in to two categories: in-band signals and out-of-band signals. In-band signals always belong to a certain bus transaction and are only valid between
stb
being set and the according response (err
orack
). being set. In contrast, the out-of-band signals are not associated with any bus transaction and are always valid when set.bus_req_t
out-of-band signalsfence
- Data/instruction fence request; single-shotsleep
- Set if ALL upstream devices are in sleep-modedebug
- Set if the upstream device is in debug-mode