I am writing to request assistance with an issue we are experiencing related to transaction handling and channel slice management in our system.
Issue Details:
Subordinate Support Limitation: Our current setup supports a maximum of 4 outstanding transactions. We are encountering limitations when attempting to manage additional transactions.
Master Response Channel Unavailability: The master response channel is currently not ready, resulting in the response channel slice being fully occupied with 4 transactions.
Address Channel Slice Management: As the address channel slice becomes available, we are considering accepting a 5th address transaction. However, we plan to store it in the slice without processing the write data channel until the master processes the response for the initial transactions.
Request for Guidance:
We seek your guidance on the following points:
Is it feasible to accept a 5th address transaction and store it in the slice under these conditions?Are there recommended practices or configurations to manage this scenario effectively?What potential risks or issues should we be aware of in implementing this approach?
Yes, this is feasible.
I would not expect there to be any specific issues caused by this as the request could be buffered at any point upstream of this, and AXI allows for independent registering on each channel - see A2.5 of the AXI Issue L Specification.