diff options
author | Sinan Kaya <okaya@codeaurora.org> | 2016-08-31 11:10:29 -0400 |
---|---|---|
committer | Vinod Koul <vinod.koul@intel.com> | 2016-08-31 21:27:32 +0530 |
commit | 793ae66c7dcc7e6655029f6613221a111b15b58e (patch) | |
tree | d5d0458836e846247b0f0ebb20d842dbe5a3df09 /drivers/dma/fsl_raid.c | |
parent | 55c370e5198e8cf28b1529299e9c1bfe237c9c1e (diff) | |
download | linux-stable-793ae66c7dcc7e6655029f6613221a111b15b58e.tar.gz linux-stable-793ae66c7dcc7e6655029f6613221a111b15b58e.tar.bz2 linux-stable-793ae66c7dcc7e6655029f6613221a111b15b58e.zip |
dmaengine: qcom_hidma: add error reporting for tx_status
The HIDMA driver is capable of error detection. However, the error was
not being passed back to the client when tx_status API is called.
Changing the error handling behavior to follow this oder.
1. dmaengine asserts error interrupt
2. Driver receives and mark's the txn as error
3. Driver completes the txn and intimates the client. No further
submissions. Drop the locks before calling callback, as subsequent
processing by client maybe in callback thread.
4. Client invokes status and you can return error
5. On error, client calls terminate_all. You can reset channel, free all
descriptors in the active, pending and completed lists
6. Client prepares new txn and so on.
As part of this work, got rid of the reset in the interrupt handler when
an error happens and the HW is put into disabled state. The only way to
recover is for the client to terminate the channel.
Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'drivers/dma/fsl_raid.c')
0 files changed, 0 insertions, 0 deletions