-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added DMA configurable timeout register #1246
base: pre-release
Are you sure you want to change the base?
Conversation
@ruck314 I think I also need to set 'timeout' register here: https://github.com/slaclab/axi-pcie-core/blob/211890d800e999ea496442d8b279f983c9d89734/protocol/gpuAsync/rtl/AxiPcieGpuAsyncControl.vhd#L302. Do you agree? |
@mmishra9 Let me know when you have completed your building and regression testing with hardware. After you are done with that, then I will approve and merge the PR. |
Co-authored-by: Jeremy L. <[email protected]>
Also getting a build error from missing |
The issues should be fixed now. |
v.axiWriteMaster.wdata(3) := dmaWrDescRet(descIndex).continue; | ||
v.axiWriteMaster.wdata(2 downto 0) := dmaWrDescRet(descIndex).result; | ||
v.axiWriteMaster.wdata(7 downto 5) := (others => '0'); | ||
v.axiWriteMaster.wdata(4) := dmaWrDescRet(descIndex).continue; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mmishra9 I am worried about backwards compatibly with his change
@JJL772 & @slacrherbst What's your opinion about this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about like this?
v.axiWriteMaster.wdata(7 downto 5) := (others => '0');
v.axiWriteMaster.wdata(4) := dmaWrDescRet(descIndex).result(3);
v.axiWriteMaster.wdata(3) := dmaWrDescRet(descIndex).continue;
v.axiWriteMaster.wdata(2 downto 0) := dmaWrDescRet(descIndex).result(2 downto 0);__
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as there is a way to change behavior based on firmware version it's okay with me. Might require some ugly code in the driver though.
Added configurable timeout register to acknowledge the timeout
Description
Added a configurable timeout register which was earlier hardcoded. If timeout reg value is reached before the write transactions are completed, the descriptor is returned.