You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In current code, message "Engine was not running!!! Clearing status\n" is printed with dbg_tfr macro that only prints when module is built with LIBXDMA_DEBUG flag. However, building with this flag enables many other debug messages and bloats the log. I suggest to replace dbg_tfr with pr_err for this message. This message only appears when XDMA IP says that transaction is complete but the kernel module did not expect that (because it timed out previously or some other error). In other words, this message shows that there was a synchronization issue between requester and completer parts of the driver. So this message should be a good starting point for further diagnostics
The text was updated successfully, but these errors were encountered:
In current code, message "Engine was not running!!! Clearing status\n" is printed with dbg_tfr macro that only prints when module is built with LIBXDMA_DEBUG flag. However, building with this flag enables many other debug messages and bloats the log. I suggest to replace dbg_tfr with pr_err for this message. This message only appears when XDMA IP says that transaction is complete but the kernel module did not expect that (because it timed out previously or some other error). In other words, this message shows that there was a synchronization issue between requester and completer parts of the driver. So this message should be a good starting point for further diagnostics
The text was updated successfully, but these errors were encountered: