All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Damien Horsley <Damien.Horsley@imgtec.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>,
	James Hartley <James.Hartley@imgtec.com>
Subject: Re: [PATCH] dma: mdc: Correct terminate_all handling
Date: Thu, 10 Dec 2015 09:50:29 +0530	[thread overview]
Message-ID: <20151210042029.GQ1854@localhost> (raw)
In-Reply-To: <5665BAFD.1010406@imgtec.com>

On Mon, Dec 07, 2015 at 04:59:41PM +0000, Damien Horsley wrote:
> On 05/12/15 08:43, Vinod Koul wrote:
> > On Mon, Nov 23, 2015 at 02:22:04PM +0000, Damien Horsley wrote:
> >> From: "Damien.Horsley" <Damien.Horsley@imgtec.com>
> >>
> >> Use of the CANCEL bit in mdc_terminate_all creates an
> >> additional 'command done' to appear in the registers (in
> >> addition to an interrupt).
> >>
> >> In addition, there is a potential race between
> >> mdc_terminate_all and the irq handler if a transfer
> >> completes at the same time as the terminate all (presently
> >> this results in an inappropriate warning).
> >>
> >> To handle these issues, any outstanding 'command done'
> >> events are cleared during mdc_terminate_all and the irq
> >> handler takes no action when there are no new 'command done'
> >> events.
> > 
> > SO what does 'command done' event represent, and what would be the behaviour
> > of ignoring those
> > 
> 
> The 'command done' event occurs whenever a new descriptor is loaded from
> memory, and once when the whole transfer is completed. Use of the CANCEL
> bit can cause additional 'command done' events to occur, which need to
> be cleared.

Okay, btw please fix the subsystem name. I'ts dmaengine

-- 
~Vinod

      reply	other threads:[~2015-12-10  4:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1448288524-21572-1-git-send-email-Damien.Horsley@imgtec.com>
2015-12-05  8:43 ` [PATCH] dma: mdc: Correct terminate_all handling Vinod Koul
2015-12-07 16:59   ` Damien Horsley
2015-12-10  4:20     ` Vinod Koul [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151210042029.GQ1854@localhost \
    --to=vinod.koul@intel.com \
    --cc=Damien.Horsley@imgtec.com \
    --cc=James.Hartley@imgtec.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.