From: Vinod Koul <vinod.koul@intel.com>
To: Stephen Barber <smbarber@chromium.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Hsin-Yu Chao <hychao@chromium.org>
Subject: Re: [PATCH] dmaengine: pl330: fix residual for non-running BUSY descriptors
Date: Fri, 9 Sep 2016 17:19:35 +0530 [thread overview]
Message-ID: <20160909114935.GP9355@localhost> (raw)
In-Reply-To: <1471568399-35770-1-git-send-email-smbarber@chromium.org>
On Thu, Aug 18, 2016 at 05:59:59PM -0700, Stephen Barber wrote:
> Only one descriptor in the work list should be running at
> any given time, but it's possible to have an enqueued BUSY
> descriptor that has not yet transferred any data, or for
> a BUSY descriptor to linger briefly before transitioning
> to DONE. These cases should be handled to keep residual
> calculations consistent even with the non-running BUSY
> descriptors in the work list.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2016-09-09 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 0:59 [PATCH] dmaengine: pl330: fix residual for non-running BUSY descriptors Stephen Barber
2016-09-09 11:49 ` 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=20160909114935.GP9355@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dianders@chromium.org \
--cc=dmaengine@vger.kernel.org \
--cc=hychao@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smbarber@chromium.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.