From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] dmaengine: at_xdmac: fix residue computation
Date: Thu, 10 Mar 2016 16:37:19 +0530 [thread overview]
Message-ID: <20160310110718.GE11154@localhost> (raw)
In-Reply-To: <1457601481-17405-1-git-send-email-ludovic.desroches@atmel.com>
On Thu, Mar 10, 2016 at 10:17:55AM +0100, Ludovic Desroches wrote:
> When computing the residue we need two pieces of information: the current
> descriptor and the remaining data of the current descriptor. To get
> that information, we need to read consecutively two registers but we
> can't do it in an atomic way. For that reason, we have to check manually
> that current descriptor has not changed.
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: david.engraf@sysgo.com, dmaengine@vger.kernel.org,
cyrille.pitchen@atmel.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, nicolas.ferre@atmel.com
Subject: Re: [RESEND PATCH] dmaengine: at_xdmac: fix residue computation
Date: Thu, 10 Mar 2016 16:37:19 +0530 [thread overview]
Message-ID: <20160310110718.GE11154@localhost> (raw)
In-Reply-To: <1457601481-17405-1-git-send-email-ludovic.desroches@atmel.com>
On Thu, Mar 10, 2016 at 10:17:55AM +0100, Ludovic Desroches wrote:
> When computing the residue we need two pieces of information: the current
> descriptor and the remaining data of the current descriptor. To get
> that information, we need to read consecutively two registers but we
> can't do it in an atomic way. For that reason, we have to check manually
> that current descriptor has not changed.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2016-03-10 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 9:17 [RESEND PATCH] dmaengine: at_xdmac: fix residue computation Ludovic Desroches
2016-03-10 9:17 ` Ludovic Desroches
2016-03-10 11:07 ` Vinod Koul [this message]
2016-03-10 11:07 ` Vinod Koul
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=20160310110718.GE11154@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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.