From: Antonio Borneo <[email protected]>
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") broke the
logic around ds_run/ds_done in case of non-cyclic DMA.
This went unnoticed as the only user of k3dma was the i2s
audio driver, but with a patch set to enable dma on SPI,
the issue cropped up.
This patch resolves the issue by reverting part of the
problematic commit.
This patch has been tested to ensure both audio playback and SPI
works fine using DMA and that no memory leak is present.
Cc: Vinod Koul <[email protected]>
Cc: Dan Williams <[email protected]>
Cc: Zhangfei Gao <[email protected]>
Cc: [email protected]
Signed-off-by: Antonio Borneo <[email protected]>
[jstultz: Expanded commit message a bit]
Signed-off-by: John Stultz <[email protected]>
---
drivers/dma/k3dma.c | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/dma/k3dma.c b/drivers/dma/k3dma.c
index 01e25c6..01d2a75 100644
--- a/drivers/dma/k3dma.c
+++ b/drivers/dma/k3dma.c
@@ -223,7 +223,6 @@ static irqreturn_t k3_dma_int_handler(int irq, void *dev_id)
if (c && (tc1 & BIT(i))) {
spin_lock_irqsave(&c->vc.lock, flags);
vchan_cookie_complete(&p->ds_run->vd);
- WARN_ON_ONCE(p->ds_done);
p->ds_done = p->ds_run;
p->ds_run = NULL;
spin_unlock_irqrestore(&c->vc.lock, flags);
@@ -274,13 +273,14 @@ static int k3_dma_start_txd(struct k3_dma_chan *c)
*/
list_del(&ds->vd.node);
- WARN_ON_ONCE(c->phy->ds_run);
- WARN_ON_ONCE(c->phy->ds_done);
c->phy->ds_run = ds;
+ c->phy->ds_done = NULL;
/* start dma */
k3_dma_set_desc(c->phy, &ds->desc_hw[0]);
return 0;
}
+ c->phy->ds_run = NULL;
+ c->phy->ds_done = NULL;
return -EAGAIN;
}
@@ -722,11 +722,7 @@ static int k3_dma_terminate_all(struct dma_chan *chan)
k3_dma_free_desc(&p->ds_run->vd);
p->ds_run = NULL;
}
- if (p->ds_done) {
- k3_dma_free_desc(&p->ds_done->vd);
- p->ds_done = NULL;
- }
-
+ p->ds_done = NULL;
}
spin_unlock_irqrestore(&c->vc.lock, flags);
vchan_dma_desc_free_list(&c->vc, &head);
--
2.7.4
On 2017年07月11日 04:53, John Stultz wrote:
> From: Antonio Borneo <[email protected]>
>
> Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
> memory handling in preparation for cyclic mode") broke the
> logic around ds_run/ds_done in case of non-cyclic DMA.
>
> This went unnoticed as the only user of k3dma was the i2s
> audio driver, but with a patch set to enable dma on SPI,
> the issue cropped up.
>
> This patch resolves the issue by reverting part of the
> problematic commit.
>
> This patch has been tested to ensure both audio playback and SPI
> works fine using DMA and that no memory leak is present.
>
> Cc: Vinod Koul <[email protected]>
> Cc: Dan Williams <[email protected]>
> Cc: Zhangfei Gao <[email protected]>
> Cc: [email protected]
> Signed-off-by: Antonio Borneo <[email protected]>
> [jstultz: Expanded commit message a bit]
> Signed-off-by: John Stultz <[email protected]>
Acked-by: Zhangfei Gao <[email protected]>
Thanks
On Mon, Jul 10, 2017 at 01:53:43PM -0700, John Stultz wrote:
> From: Antonio Borneo <[email protected]>
>
> Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
> memory handling in preparation for cyclic mode") broke the
> logic around ds_run/ds_done in case of non-cyclic DMA.
>
> This went unnoticed as the only user of k3dma was the i2s
> audio driver, but with a patch set to enable dma on SPI,
> the issue cropped up.
>
> This patch resolves the issue by reverting part of the
> problematic commit.
Can you explain the fix here, how reverting helps around with that?
Right now am not able to comprehend the fix on this..
> This patch has been tested to ensure both audio playback and SPI
> works fine using DMA and that no memory leak is present.
>
> Cc: Vinod Koul <[email protected]>
> Cc: Dan Williams <[email protected]>
> Cc: Zhangfei Gao <[email protected]>
> Cc: [email protected]
> Signed-off-by: Antonio Borneo <[email protected]>
> [jstultz: Expanded commit message a bit]
> Signed-off-by: John Stultz <[email protected]>
> ---
> drivers/dma/k3dma.c | 12 ++++--------
> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/dma/k3dma.c b/drivers/dma/k3dma.c
> index 01e25c6..01d2a75 100644
> --- a/drivers/dma/k3dma.c
> +++ b/drivers/dma/k3dma.c
> @@ -223,7 +223,6 @@ static irqreturn_t k3_dma_int_handler(int irq, void *dev_id)
> if (c && (tc1 & BIT(i))) {
> spin_lock_irqsave(&c->vc.lock, flags);
> vchan_cookie_complete(&p->ds_run->vd);
> - WARN_ON_ONCE(p->ds_done);
> p->ds_done = p->ds_run;
> p->ds_run = NULL;
> spin_unlock_irqrestore(&c->vc.lock, flags);
> @@ -274,13 +273,14 @@ static int k3_dma_start_txd(struct k3_dma_chan *c)
> */
> list_del(&ds->vd.node);
>
> - WARN_ON_ONCE(c->phy->ds_run);
> - WARN_ON_ONCE(c->phy->ds_done);
Not sure why WARN_ON should be removed?
> c->phy->ds_run = ds;
> + c->phy->ds_done = NULL;
> /* start dma */
> k3_dma_set_desc(c->phy, &ds->desc_hw[0]);
> return 0;
> }
> + c->phy->ds_run = NULL;
> + c->phy->ds_done = NULL;
> return -EAGAIN;
> }
>
> @@ -722,11 +722,7 @@ static int k3_dma_terminate_all(struct dma_chan *chan)
> k3_dma_free_desc(&p->ds_run->vd);
> p->ds_run = NULL;
> }
> - if (p->ds_done) {
> - k3_dma_free_desc(&p->ds_done->vd);
> - p->ds_done = NULL;
> - }
> -
> + p->ds_done = NULL;
> }
> spin_unlock_irqrestore(&c->vc.lock, flags);
> vchan_dma_desc_free_list(&c->vc, &head);
> --
> 2.7.4
>
--
~Vinod
On Tue, Jul 18, 2017 at 5:58 PM, Vinod Koul <[email protected]> wrote:
> On Mon, Jul 10, 2017 at 01:53:43PM -0700, John Stultz wrote:
>> From: Antonio Borneo <[email protected]>
>>
>> Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
>> memory handling in preparation for cyclic mode") broke the
>> logic around ds_run/ds_done in case of non-cyclic DMA.
>>
>> This went unnoticed as the only user of k3dma was the i2s
>> audio driver, but with a patch set to enable dma on SPI,
>> the issue cropped up.
>>
>> This patch resolves the issue by reverting part of the
>> problematic commit.
>
> Can you explain the fix here, how reverting helps around with that?
> Right now am not able to comprehend the fix on this..
>
Hi Vinod,
thanks for your review.
The structure of the driver k3dma seams inspired to zx_dma that uses
the same ds_run/ds_done method.
This driver k3dma was already working fine for non-cyclic use cases, like SPI.
While preparing support for cyclic mode, the commit above removed some
assignment to NULL for ds_run/ds_done at the end of the non-cyclic DMA
transfer. As result, only the first non-cyclic DMA transfer completes
successfully, the following non-cyclic DMA transfer hangs (plus it
triggers one WARN_ON() because of the missing NULL initialization).
The main target of this patch is to re-add the NULL assignments.
>> This patch has been tested to ensure both audio playback and SPI
>> works fine using DMA and that no memory leak is present.
>>
>> Cc: Vinod Koul <[email protected]>
>> Cc: Dan Williams <[email protected]>
>> Cc: Zhangfei Gao <[email protected]>
>> Cc: [email protected]
>> Signed-off-by: Antonio Borneo <[email protected]>
>> [jstultz: Expanded commit message a bit]
>> Signed-off-by: John Stultz <[email protected]>
>> ---
>> drivers/dma/k3dma.c | 12 ++++--------
>> 1 file changed, 4 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/dma/k3dma.c b/drivers/dma/k3dma.c
>> index 01e25c6..01d2a75 100644
>> --- a/drivers/dma/k3dma.c
>> +++ b/drivers/dma/k3dma.c
>> @@ -223,7 +223,6 @@ static irqreturn_t k3_dma_int_handler(int irq, void *dev_id)
>> if (c && (tc1 & BIT(i))) {
>> spin_lock_irqsave(&c->vc.lock, flags);
>> vchan_cookie_complete(&p->ds_run->vd);
>> - WARN_ON_ONCE(p->ds_done);
>> p->ds_done = p->ds_run;
>> p->ds_run = NULL;
>> spin_unlock_irqrestore(&c->vc.lock, flags);
>> @@ -274,13 +273,14 @@ static int k3_dma_start_txd(struct k3_dma_chan *c)
>> */
>> list_del(&ds->vd.node);
>>
>> - WARN_ON_ONCE(c->phy->ds_run);
>> - WARN_ON_ONCE(c->phy->ds_done);
>
> Not sure why WARN_ON should be removed?
The commit above added them. Now that the logic on ds_run/ds_done is
fixed, I do not see reason for them anymore.
Best Regards
Antonio
>
>> c->phy->ds_run = ds;
>> + c->phy->ds_done = NULL;
>> /* start dma */
>> k3_dma_set_desc(c->phy, &ds->desc_hw[0]);
>> return 0;
>> }
>> + c->phy->ds_run = NULL;
>> + c->phy->ds_done = NULL;
>> return -EAGAIN;
>> }
>>
>> @@ -722,11 +722,7 @@ static int k3_dma_terminate_all(struct dma_chan *chan)
>> k3_dma_free_desc(&p->ds_run->vd);
>> p->ds_run = NULL;
>> }
>> - if (p->ds_done) {
>> - k3_dma_free_desc(&p->ds_done->vd);
>> - p->ds_done = NULL;
>> - }
>> -
>> + p->ds_done = NULL;
>> }
>> spin_unlock_irqrestore(&c->vc.lock, flags);
>> vchan_dma_desc_free_list(&c->vc, &head);
>> --
>> 2.7.4
>>
>
> --
> ~Vinod
On Wed, Jul 19, 2017 at 12:29:55AM +0200, Antonio Borneo wrote:
> On Tue, Jul 18, 2017 at 5:58 PM, Vinod Koul <[email protected]> wrote:
> > On Mon, Jul 10, 2017 at 01:53:43PM -0700, John Stultz wrote:
> >> From: Antonio Borneo <[email protected]>
> >>
> >> Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
> >> memory handling in preparation for cyclic mode") broke the
> >> logic around ds_run/ds_done in case of non-cyclic DMA.
> >>
> >> This went unnoticed as the only user of k3dma was the i2s
> >> audio driver, but with a patch set to enable dma on SPI,
> >> the issue cropped up.
> >>
> >> This patch resolves the issue by reverting part of the
> >> problematic commit.
> >
> > Can you explain the fix here, how reverting helps around with that?
> > Right now am not able to comprehend the fix on this..
> >
>
> Hi Vinod,
>
> thanks for your review.
>
> The structure of the driver k3dma seams inspired to zx_dma that uses
> the same ds_run/ds_done method.
> This driver k3dma was already working fine for non-cyclic use cases, like SPI.
> While preparing support for cyclic mode, the commit above removed some
> assignment to NULL for ds_run/ds_done at the end of the non-cyclic DMA
> transfer. As result, only the first non-cyclic DMA transfer completes
> successfully, the following non-cyclic DMA transfer hangs (plus it
> triggers one WARN_ON() because of the missing NULL initialization).
>
> The main target of this patch is to re-add the NULL assignments.
Okay so fix is only adding NULL assignments, and which was not at all clear
from the changelog. The changelog need to give reviewers and maintainers and
idea on why a change was done and the details of the fix.
> >> This patch has been tested to ensure both audio playback and SPI
> >> works fine using DMA and that no memory leak is present.
> >>
> >> Cc: Vinod Koul <[email protected]>
> >> Cc: Dan Williams <[email protected]>
> >> Cc: Zhangfei Gao <[email protected]>
> >> Cc: [email protected]
> >> Signed-off-by: Antonio Borneo <[email protected]>
> >> [jstultz: Expanded commit message a bit]
> >> Signed-off-by: John Stultz <[email protected]>
> >> ---
> >> drivers/dma/k3dma.c | 12 ++++--------
> >> 1 file changed, 4 insertions(+), 8 deletions(-)
> >>
> >> diff --git a/drivers/dma/k3dma.c b/drivers/dma/k3dma.c
> >> index 01e25c6..01d2a75 100644
> >> --- a/drivers/dma/k3dma.c
> >> +++ b/drivers/dma/k3dma.c
> >> @@ -223,7 +223,6 @@ static irqreturn_t k3_dma_int_handler(int irq, void *dev_id)
> >> if (c && (tc1 & BIT(i))) {
> >> spin_lock_irqsave(&c->vc.lock, flags);
> >> vchan_cookie_complete(&p->ds_run->vd);
> >> - WARN_ON_ONCE(p->ds_done);
> >> p->ds_done = p->ds_run;
> >> p->ds_run = NULL;
> >> spin_unlock_irqrestore(&c->vc.lock, flags);
> >> @@ -274,13 +273,14 @@ static int k3_dma_start_txd(struct k3_dma_chan *c)
> >> */
> >> list_del(&ds->vd.node);
> >>
> >> - WARN_ON_ONCE(c->phy->ds_run);
> >> - WARN_ON_ONCE(c->phy->ds_done);
> >
> > Not sure why WARN_ON should be removed?
>
> The commit above added them. Now that the logic on ds_run/ds_done is
> fixed, I do not see reason for them anymore.
Since this is not a revert and only fix, I would prefer this to be removed
from fix, if you want to remove these please do send a second patch as this
has nothing to do with the fix
While at it, also change the patch title to dmaengine: ....
Thanks
--
~Vinod
On Wed, Jul 19, 2017 at 5:47 AM, Vinod Koul <[email protected]> wrote:
> On Wed, Jul 19, 2017 at 12:29:55AM +0200, Antonio Borneo wrote:
>> On Tue, Jul 18, 2017 at 5:58 PM, Vinod Koul <[email protected]> wrote:
>> > On Mon, Jul 10, 2017 at 01:53:43PM -0700, John Stultz wrote:
>> >> From: Antonio Borneo <[email protected]>
>> >>
>> >> Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
>> >> memory handling in preparation for cyclic mode") broke the
>> >> logic around ds_run/ds_done in case of non-cyclic DMA.
>> >>
>> >> This went unnoticed as the only user of k3dma was the i2s
>> >> audio driver, but with a patch set to enable dma on SPI,
>> >> the issue cropped up.
>> >>
>> >> This patch resolves the issue by reverting part of the
>> >> problematic commit.
>> >
>> > Can you explain the fix here, how reverting helps around with that?
>> > Right now am not able to comprehend the fix on this..
>> >
>>
>> Hi Vinod,
>>
>> thanks for your review.
>>
>> The structure of the driver k3dma seams inspired to zx_dma that uses
>> the same ds_run/ds_done method.
>> This driver k3dma was already working fine for non-cyclic use cases, like SPI.
>> While preparing support for cyclic mode, the commit above removed some
>> assignment to NULL for ds_run/ds_done at the end of the non-cyclic DMA
>> transfer. As result, only the first non-cyclic DMA transfer completes
>> successfully, the following non-cyclic DMA transfer hangs (plus it
>> triggers one WARN_ON() because of the missing NULL initialization).
>>
>> The main target of this patch is to re-add the NULL assignments.
>
> Okay so fix is only adding NULL assignments, and which was not at all clear
> from the changelog. The changelog need to give reviewers and maintainers and
> idea on why a change was done and the details of the fix.
Ok, I will make it clear in V2
>
>> >> This patch has been tested to ensure both audio playback and SPI
>> >> works fine using DMA and that no memory leak is present.
>> >>
>> >> Cc: Vinod Koul <[email protected]>
>> >> Cc: Dan Williams <[email protected]>
>> >> Cc: Zhangfei Gao <[email protected]>
>> >> Cc: [email protected]
>> >> Signed-off-by: Antonio Borneo <[email protected]>
>> >> [jstultz: Expanded commit message a bit]
>> >> Signed-off-by: John Stultz <[email protected]>
>> >> ---
>> >> drivers/dma/k3dma.c | 12 ++++--------
>> >> 1 file changed, 4 insertions(+), 8 deletions(-)
>> >>
>> >> diff --git a/drivers/dma/k3dma.c b/drivers/dma/k3dma.c
>> >> index 01e25c6..01d2a75 100644
>> >> --- a/drivers/dma/k3dma.c
>> >> +++ b/drivers/dma/k3dma.c
>> >> @@ -223,7 +223,6 @@ static irqreturn_t k3_dma_int_handler(int irq, void *dev_id)
>> >> if (c && (tc1 & BIT(i))) {
>> >> spin_lock_irqsave(&c->vc.lock, flags);
>> >> vchan_cookie_complete(&p->ds_run->vd);
>> >> - WARN_ON_ONCE(p->ds_done);
>> >> p->ds_done = p->ds_run;
>> >> p->ds_run = NULL;
>> >> spin_unlock_irqrestore(&c->vc.lock, flags);
>> >> @@ -274,13 +273,14 @@ static int k3_dma_start_txd(struct k3_dma_chan *c)
>> >> */
>> >> list_del(&ds->vd.node);
>> >>
>> >> - WARN_ON_ONCE(c->phy->ds_run);
>> >> - WARN_ON_ONCE(c->phy->ds_done);
>> >
>> > Not sure why WARN_ON should be removed?
>>
>> The commit above added them. Now that the logic on ds_run/ds_done is
>> fixed, I do not see reason for them anymore.
>
> Since this is not a revert and only fix, I would prefer this to be removed
> from fix, if you want to remove these please do send a second patch as this
> has nothing to do with the fix
>
> While at it, also change the patch title to dmaengine: ....
Ok, I will split it and change the title.
Thanks
Antonio
>
> Thanks
> --
> ~Vinod
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") broke the
logic around ds_run/ds_done in case of non-cyclic DMA.
This v2 splits the initial patch in three parts:
- the real fix for non-cyclic mode
- another fix for a double free introduced in the same commit
- cosmetic removal of useless ON_WARN_ONCE()
Thread in https://patchwork.kernel.org/patch/9833791/
v1 -> v2
- split the patch
- change patch title to "dmaengine: ..."
Antonio Borneo (3):
dmaengine: k3dma: fix non-cyclic mode
dmaengine: k3dma: fix double free of descriptor
dmaengine: k3dma: remove useless ON_WARN_ONCE()
drivers/dma/k3dma.c | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
--
1.9.1
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") adds code
to free the descriptor in ds_done.
In cyclic mode, ds_done is never used and it's always NULL,
so the added code is not executed.
In non-cyclic mode, ds_done is used as a flag: when not NULL
it signals that the descriptor has been consumed. No need to
free it because it would be free by vchan_complete().
The fix takes back the code changed by the commit above:
- remove the free on the descriptor;
- initialize ds_done to NULL for the next run.
Signed-off-by: Antonio Borneo <[email protected]>
---
To: [email protected]
To: Vinod Koul <[email protected]>
To: Dan Williams <[email protected]>
Cc: [email protected]
Cc: John Stultz <[email protected]>
Cc: Zhangfei Gao <[email protected]>
---
drivers/dma/k3dma.c | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/dma/k3dma.c b/drivers/dma/k3dma.c
index c00eb12..b769623 100644
--- a/drivers/dma/k3dma.c
+++ b/drivers/dma/k3dma.c
@@ -724,11 +724,7 @@ static int k3_dma_terminate_all(struct dma_chan *chan)
k3_dma_free_desc(&p->ds_run->vd);
p->ds_run = NULL;
}
- if (p->ds_done) {
- k3_dma_free_desc(&p->ds_done->vd);
- p->ds_done = NULL;
- }
-
+ p->ds_done = NULL;
}
spin_unlock_irqrestore(&c->vc.lock, flags);
vchan_dma_desc_free_list(&c->vc, &head);
--
1.9.1
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") adds few
calls to ON_WARN_ONCE() to track the use of ds_run/ds_done.
After the two fixes:
- dmaengine: k3dma: fix non-cyclic mode
- dmaengine: k3dma: fix re-free of the same descriptor
the behaviour of ds_run/ds_done is properly fixed.
The remaining ON_WARN_ONCE() are never triggered and can be
removed.
Signed-off-by: Antonio Borneo <[email protected]>
---
To: [email protected]
To: Vinod Koul <[email protected]>
To: Dan Williams <[email protected]>
Cc: [email protected]
Cc: John Stultz <[email protected]>
Cc: Zhangfei Gao <[email protected]>
---
drivers/dma/k3dma.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/dma/k3dma.c b/drivers/dma/k3dma.c
index b769623..01d2a75 100644
--- a/drivers/dma/k3dma.c
+++ b/drivers/dma/k3dma.c
@@ -223,7 +223,6 @@ static irqreturn_t k3_dma_int_handler(int irq, void *dev_id)
if (c && (tc1 & BIT(i))) {
spin_lock_irqsave(&c->vc.lock, flags);
vchan_cookie_complete(&p->ds_run->vd);
- WARN_ON_ONCE(p->ds_done);
p->ds_done = p->ds_run;
p->ds_run = NULL;
spin_unlock_irqrestore(&c->vc.lock, flags);
@@ -274,7 +273,6 @@ static int k3_dma_start_txd(struct k3_dma_chan *c)
*/
list_del(&ds->vd.node);
- WARN_ON_ONCE(c->phy->ds_run);
c->phy->ds_run = ds;
c->phy->ds_done = NULL;
/* start dma */
--
1.9.1
Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
memory handling in preparation for cyclic mode") broke the
logic around ds_run/ds_done in case of non-cyclic DMA.
This went unnoticed as the only user of k3dma was the i2s
audio driver but, with a patch set to enable dma on SPI, the
issue popped out.
The fix re-applies the initialization to ds_run/ds_done in
k3_dma_start_txd() that were removed by the commit above.
Also, one of the calls to k3_dma_start_txd() is triggered by
(ds_done != NULL), so remove the noisy and useless call to
WARN_ON_ONCE().
Signed-off-by: Antonio Borneo <[email protected]>
---
To: [email protected]
To: Vinod Koul <[email protected]>
To: Dan Williams <[email protected]>
Cc: [email protected]
Cc: John Stultz <[email protected]>
Cc: Zhangfei Gao <[email protected]>
---
drivers/dma/k3dma.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/k3dma.c b/drivers/dma/k3dma.c
index 01e25c6..c00eb12 100644
--- a/drivers/dma/k3dma.c
+++ b/drivers/dma/k3dma.c
@@ -275,12 +275,14 @@ static int k3_dma_start_txd(struct k3_dma_chan *c)
list_del(&ds->vd.node);
WARN_ON_ONCE(c->phy->ds_run);
- WARN_ON_ONCE(c->phy->ds_done);
c->phy->ds_run = ds;
+ c->phy->ds_done = NULL;
/* start dma */
k3_dma_set_desc(c->phy, &ds->desc_hw[0]);
return 0;
}
+ c->phy->ds_run = NULL;
+ c->phy->ds_done = NULL;
return -EAGAIN;
}
--
1.9.1
On Tue, Aug 01, 2017 at 10:09:24PM +0200, Antonio Borneo wrote:
> Commit 36387a2b1f62b5c087c5fe6f0f7b23b94f722ad7 ("k3dma: Fix
> memory handling in preparation for cyclic mode") broke the
> logic around ds_run/ds_done in case of non-cyclic DMA.
Applied, thanks
--
~Vinod