From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: Viresh Kumar <viresh.kumar@st.com>,
Kukjin Kim <kgene.kim@samsung.com>,
yuanyabin1978@sina.com, linux-kernel@vger.kernel.org,
Ben Dooks <ben-linux@fluff.org>,
Peter Pearse <peter.pearse@arm.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-arm-kernel@lists.infradead.org,
Alessandro Rubini <rubini@unipv.it>
Subject: Re: [PATCH 06/13] DMAENGINE: driver for the ARM PL080/PL081 PrimeCells
Date: Tue, 21 Dec 2010 22:25:32 +0000 [thread overview]
Message-ID: <20101221222532.GA7507@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101221182037.GA4783@n2100.arm.linux.org.uk>
On Tue, Dec 21, 2010 at 06:20:37PM +0000, Russell King - ARM Linux wrote:
> Having just looked at this while trying to undo the DMA API abuses
> in the PL011 UART driver, I'm getting rather frustrated with this
> code.
Here's another couple of problems:
PL011 driver:
+ dmatx->cookie = desc->tx_submit(desc);
+ if (dma_submit_error(dmatx->cookie)) {
+ /* "Complete" DMA (errorpath) */
+ complete(&dmatx->complete);
+ chan->device->device_control(chan, DMA_TERMINATE_ALL, 0);
+ return dmatx->cookie;
+ }
dmatx->cookie is of type dma_cookie_t, which is a s32.
MMCI driver:
+ dma_cookie_t cookie;
...
+ cookie = desc->tx_submit(desc);
+
+ /* Here overloaded DMA controllers may fail */
+ if (dma_submit_error(cookie))
+ goto unmap_exit;
#define dma_submit_error(cookie) ((cookie) < 0 ? 1 : 0)
So, DMA errors are negative values returned from the tx_submit function.
PL08x tx_submit method:
static dma_cookie_t pl08x_tx_submit(struct dma_async_tx_descriptor *tx)
{
struct pl08x_dma_chan *plchan = to_pl08x_chan(tx->chan);
atomic_inc(&plchan->last_issued);
tx->cookie = atomic_read(&plchan->last_issued);
/* This unlock follows the lock in the prep() function */
spin_unlock_irqrestore(&plchan->lock, plchan->lockflags);
return tx->cookie;
}
So, after 2^31 DMA transactions, the DMA engine layer continues happily
along with the queued DMA operation, but the driver gets a negative
cookie returned, and so bails out.
I'm also left wondering about that atomic_t. It's incremented and
read in a locked region, which will in itself prevent two concurrent
increments. The only other places its used is from dma_tx_status()
where it is only ever read, and on the initialization path. That to
me makes no sense.
I'll see if I can get to looking at the PL08x stuff once I've finished
sorting out the PL011 UART driver DMA support into a state where I'm
happy that it's doing things correctly.
next prev parent reply other threads:[~2010-12-21 22:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 15:27 Linus Walleij
2010-06-14 6:02 ` Viresh KUMAR
2010-06-14 13:39 ` Linus Walleij
2010-06-15 5:25 ` Viresh KUMAR
2010-06-15 20:14 ` Linus WALLEIJ
2010-06-16 3:59 ` Viresh KUMAR
2010-06-16 6:38 ` Linus Walleij
2010-06-15 10:25 ` Kukjin Kim
2010-06-15 10:45 ` Jassi Brar
2010-06-15 11:17 ` Maurus Cuelenaere
2010-06-15 11:39 ` Jassi Brar
2010-06-15 12:04 ` Maurus Cuelenaere
2010-06-15 20:55 ` Linus WALLEIJ
2010-12-21 18:20 ` Russell King - ARM Linux
2010-12-21 22:25 ` Russell King - ARM Linux [this message]
2010-12-22 12:22 ` Russell King - ARM Linux
2010-12-22 12:29 ` Russell King - ARM Linux
2010-12-22 23:45 ` Dan Williams
2010-12-22 23:54 ` Russell King - ARM Linux
2010-12-23 0:53 ` Dan Williams
2010-12-23 0:10 ` Russell King - ARM Linux
2010-12-23 1:11 ` Dan Williams
2010-12-23 1:31 ` Dan Williams
2010-12-31 21:50 ` Russell King - ARM Linux
2011-01-02 9:42 ` Dan Williams
2011-01-02 11:22 ` Russell King - ARM Linux
2011-01-02 20:33 ` Linus Walleij
2011-01-03 11:14 ` Russell King - ARM Linux
2010-12-23 9:18 ` Russell King - ARM Linux
2010-12-23 8:17 ` Linus Walleij
2010-12-23 8:30 ` Jassi Brar
2010-12-23 12:30 ` Russell King - ARM Linux
2010-12-28 0:33 ` Linus Walleij
2011-01-01 15:15 ` Russell King - ARM Linux
2011-01-02 20:29 ` Linus Walleij
2014-03-10 13:56 ` David Woodhouse
2014-03-10 14:11 ` Arnd Bergmann
2014-03-10 14:27 ` David Woodhouse
2014-03-10 14:40 ` Arnd Bergmann
2014-03-10 14:32 ` Russell King - ARM Linux
2014-03-10 14:52 ` David Woodhouse
2014-03-13 8:17 ` Linus Walleij
2014-03-13 8:52 ` Arnd Bergmann
2014-03-13 14:35 ` Linus Walleij
2011-01-01 15:36 ` Russell King - ARM Linux
2011-01-03 15:19 ` Russell King - ARM Linux
2011-01-04 0:41 ` Jassi Brar
2011-01-04 10:47 ` Linus Walleij
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=20101221222532.GA7507@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=ben-linux@fluff.org \
--cc=dan.j.williams@intel.com \
--cc=kgene.kim@samsung.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.pearse@arm.com \
--cc=rubini@unipv.it \
--cc=viresh.kumar@st.com \
--cc=yuanyabin1978@sina.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
all inboxes | Powered by JetHome®