From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/2] sDMA descriptor autoloading feature
Date: Fri, 27 Aug 2010 20:39:10 +0100 [thread overview]
Message-ID: <20100827193910.GG23079@void.printf.net> (raw)
In-Reply-To: <i2x618f0c911004291034g7f5b377ds5efaf74c901bc036@mail.gmail.com>
Hi Venkatraman,
On Thu, Apr 29, 2010 at 11:04:34PM +0530, Venkatraman S wrote:
> This patch series is the introduction of new sDMA feature: descriptor
> autoloading (v8) and it's adoption by the OMAP HSMMC driver.
>
> The previous version (v7) was blocked on achieving proper interrupt
> syncronisation
> between the MMC and DMA callback in the HSMMC driver.
> Thanks to Adrian Hunter's patch, https://patchwork.kernel.org/patch/94670/
> this has been cleaned up.
>
> Current version is based on for-next branch + Adrian Hunter's
> interrupt syncronisation patch
> (https://patchwork.kernel.org/patch/94670)
>
> Changes since v7:
> * Removed the 'fix race condition between DMA and HSMMC callback'
> part of the series
> * Added memory barries in start and resume sglist transfer for cpu
> buffer syncronization
> * Cleanup and comments
>
> This has been tested on OMAP3430, OMAP3630 and OMAP4430 SDP
> for MMC file transfer and as boot file system.
The comments on this patchset were positive apart from some stylistic
changes -- would you like to resubmit a new patch?
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2010-08-27 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 17:34 [PATCH v8 0/2] sDMA descriptor autoloading feature Venkatraman S
2010-05-04 23:15 ` Madhusudhan
2010-05-05 4:38 ` Venkatraman S
2010-05-05 9:32 ` Shilimkar, Santosh
2010-08-27 19:39 ` Chris Ball [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=20100827193910.GG23079@void.printf.net \
--to=cjb@laptop.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).