From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: <jouko.haapaluoma@wapice.com>
Cc: <Sami.Pietikainen@wapice.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<vinod.koul@intel.com>, Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: [RFC PATCH 0/2] dmaengine: at_hdmac: fix locking according to slave DMA requirements
Date: Mon, 27 Jan 2014 15:23:22 +0100 [thread overview]
Message-ID: <cover.1390832343.git.nicolas.ferre@atmel.com> (raw)
In-Reply-To: <C9F8415089354E4FB76F4548B3515AF484286F61@edb1.wapice.localdomain>
Hi,
This is an attempt to solve the locking issue that we currently have with the
Atmel at_hdmac dmaengine driver.
I tested these patches with several drivers but may need more coverage before
making them permanent...
Comments welcome.
Nicolas Ferre (2):
dmaengine: at_hdmac: remove the call to issue_pending from tx_status
dmaengine: at_hdmac: run callback function with no lock held nor
interrupts disabled
drivers/dma/at_hdmac.c | 128 +++++++++++++++++++++++++++----------------------
1 file changed, 71 insertions(+), 57 deletions(-)
--
1.8.2.2
next parent reply other threads:[~2014-01-27 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C9F8415089354E4FB76F4548B3515AF484286F61@edb1.wapice.localdomain>
2014-01-27 14:23 ` Nicolas Ferre [this message]
2014-01-27 14:23 ` [PATCH 1/2] dmaengine: at_hdmac: remove the call to issue_pending from tx_status Nicolas Ferre
2014-01-27 14:23 ` [PATCH 2/2] dmaengine: at_hdmac: run callback function with no lock held nor interrupts disabled Nicolas Ferre
2014-03-11 10:56 ` Vinod Koul
2014-01-31 10:56 ` [RFC PATCH 0/2] dmaengine: at_hdmac: fix locking according to slave DMA requirements Jouko Haapaluoma
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=cover.1390832343.git.nicolas.ferre@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=Sami.Pietikainen@wapice.com \
--cc=dmaengine@vger.kernel.org \
--cc=jouko.haapaluoma@wapice.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).