From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmci: make sure DMA transfers wait for FIFO drain
Date: Fri, 11 Feb 2011 11:30:20 +0100 [thread overview]
Message-ID: <AANLkTikOArp9y4bTsvKCxtShoTzzsQeABfPn0z+dGneL@mail.gmail.com> (raw)
In-Reply-To: <20110211101056.GB23404@n2100.arm.linux.org.uk>
2011/2/11 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> Maybe a solution to this is to use the DMA callback to signal that the
> data path has completed, but still have the data end interrupt in place
> so that it can trigger the stop command. ?That shouldn't result in
> additional delays or even the requirement for a timeout.
That should be possible, I'll try to fix up a patch like that.
Thanks,
Linus Walleij
prev parent reply other threads:[~2011-02-11 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 21:39 [PATCH] mmci: make sure DMA transfers wait for FIFO drain Linus Walleij
2011-02-01 11:03 ` Russell King - ARM Linux
2011-02-01 14:11 ` Linus Walleij
2011-02-11 9:46 ` Linus Walleij
2011-02-11 10:10 ` Russell King - ARM Linux
2011-02-11 10:30 ` Linus Walleij [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=AANLkTikOArp9y4bTsvKCxtShoTzzsQeABfPn0z+dGneL@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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 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).