Allows converting a list of key into values.
Allows converting a list of key into values. ex : node(1 to 2)(MY_STAGEABLE)
Return the hardware signal for this Payload key at the point of this Node in the pipeline.
Return the hardware signal for this (Payload, subKey) key at the point of this Node in the pipeline.
Return the hardware signal for this (Payload, subKey) key at the point of this Node in the pipeline.
This eases the construction of multi-lane hardware. For instance, when you have a
multi-issue CPU pipeline, you can use the lane Int id as secondary key.
The signal which specifies if the node’s transaction in being canceled from the pipeline.
The signal which specifies if the node’s transaction in being canceled from the pipeline.
It is driven by the downstream. The signal has no meaning when there is no transaction (valid being deasserted).
Created on demand, thus it's important to use isReady to get the signal value.
Return a new Payload which is connected to the given Data hardware signal starting from this Node in the pipeline.
Return a new Payload which is connected to the given Data hardware signal starting from this Node in the pipeline.
Read-only accessor of cancel
Read-only accessor of cancel
True when the node transaction is being cleaned up.
True when the node transaction is being cleaned up.
Meaning that it will not appear anywhere in the pipeline in future cycles.
It is equivalent to isValid && isCancel.
True when the current transaction is successfully moving forward (isReady && !isRemoved).
True when the current transaction is successfully moving forward (isReady && !isRemoved).
Useful to validate state changes.
True when it is the last cycle that the current transaction is present on this node.
True when it is the last cycle that the current transaction is present on this node.
More precisely, True when the node transaction will not be present anymore on the node
(starting from the next cycle), either because downstream is ready to take the transaction, or
because the transaction is canceled from the pipeline. (valid && (ready || cancel)).
Useful to “reset” states.
Read-only accessor of ready
Read-only accessor of ready
Read-only accessor of valid
Read-only accessor of valid
The signal which specifies if the node’s transaction can proceed downstream.
The signal which specifies if the node’s transaction can proceed downstream.
It is driven by the downstream to create backpressure. The signal has no meaning when there is no transaction (valid being deasserted).
Created on demand, thus it's important to use isReady to get the signal value.
The signal which specifies if a transaction is present on the node.
The signal which specifies if a transaction is present on the node.
It is driven by the upstream. Once asserted, it must only be de-asserted the cycle after which either both valid and ready or cancel are high. valid must not depend on ready.
Created on demand, thus it's important to use isValid to get the signal value.
(Since version ) see corresponding Javadoc for more information.