user/sven/linux.git/drivers/dma/cppi41.c, branch v3.18.84

dma: cppi41: Switch to using managed resource in probe

2014-10-15T14:56:45Z

This change uses managed resource APIs to allocate resources such as, mem, irq in order to simplify the driver unload or failure cases Signed-off-by: Kiran Padwal Signed-off-by: Vinod Koul

dma: cppi41: handle 0-length packets

2014-07-01T06:45:48Z

When a 0-length packet is received on the bus, desc->pd0 yields 1, which confuses the driver's users. This information is clearly wrong and not in accordance to the datasheet, but it's been observed on an AM335x board, very reproducible. Fix this by looking at bit 19 in PD2 of the completed packet. This bit will tell us if a zero-length packet was received on a queue. If it's set, ignore the value in PD0 and report a total length of 0 instead. Signed-off-by: Daniel Mack Signed-off-by: Vinod Koul

dma: cppi41: start tear down only if channel is busy

2014-03-11T10:52:43Z

Start the channel tear down only if the channel is busy, else just bail out. In some cases its seen that by the time the tear down is initiated the cppi completes the DMA, especially in ISOCH transfers. Signed-off-by: George Cherian Signed-off-by: Vinod Koul

drivers/dma: fix error return code

2014-01-20T09:28:03Z

Set the return variable to an error code as done elsewhere in the function. A simplified version of the semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // ( if@p1 (\(ret < 0\|ret != 0\)) { ... return ret; } | ret@p1 = 0 ) ... when != ret = e1 when != &ret *if(...) { ... when != ret = e2 when forall return ret; } // Signed-off-by: Julia Lawall Signed-off-by: Vinod Koul

dma: cppi41: return code > 0 of pm_runtime_get_sync() is not an error

2013-11-12T08:58:25Z

Return code of pm_runtime_get_sync() > 0 is not an error and may happen. Noticed during rmmod & modprobe testing. Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Vinod Koul

dma: cppi41: redo descriptor collection in abort case

2013-11-12T08:58:24Z

Most of the logic here is try and error since what actually happens does not match the trm or I miss read it. My first assumption was that the queue on which the tear-down descriptor completes (their own complete queue vs "active descriptor" complete queue) depends on the transfer direction. This seems not to be true because I manage to trigger | WARN_ON(c->desc_phys != desc_phys); and the other few were fine means the tear-down descriptor was valid but on different queue. This patch changes the logic here to look on both queues for the descriptor. Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Vinod Koul

dma: cppi41: use cppi41_pop_desc() where possible

2013-11-12T08:58:24Z

Use cppi41_pop_desc() when appropriate instead of open-coding the same functionality again. That makes the code more readable. The function has to be moved some lines up for this change. Signed-off-by: Daniel Mack Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Vinod Koul

dma: cppi41: restore more registers

2013-11-12T08:58:24Z

With active users over suspend/resume cycles, it turns out that more registers, in particular DMA_TDFDQ and RXHPCRA0, have to be restored on resume. Signed-off-by: Daniel Mack Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Vinod Koul

dmaengine: cppi41: use DMA_COMPLETE for dma completion status

2013-10-25T05:45:57Z

Acked-by: Dan Williams Acked-by: Linus Walleij Signed-off-by: Vinod Koul

dma: cppi41: add support for suspend and resume

2013-10-07T02:11:39Z

This patch adds support for suspend/resume functionality to the cppi41 DMA driver. The steps necessary to make the system resume properly were figured out by trial-and-error. The code as it stands now is the minimum that has to be done to put the musb host system on an AM33xx system into an operable state after resume. Signed-off-by: Daniel Mack Signed-off-by: Vinod Koul