From: saeed.bishara@gmail.com (saeed bishara)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 00/11] mmc: use nonblock mmc requests to minimize latency
Date: Mon, 27 Jun 2011 13:34:48 +0300 [thread overview]
Message-ID: <BANLkTimnuEK_9RedmD1OgcunX3rPvd-O0Q@mail.gmail.com> (raw)
In-Reply-To: <20110621075319.GN26089@n2100.arm.linux.org.uk>
>
> +static inline void __dma_sync(void)
> +{
> + ? ? ? dsb();
> +}
> +
> ?/*
> ?* Return whether the given device DMA address mask can be supported
> ?* properly. ?For example, if your device can only drive the low 24-bits
> @@ -378,6 +383,7 @@ static inline dma_addr_t dma_map_single(struct device *dev, void *cpu_addr,
> ? ? ? ?BUG_ON(!valid_dma_direction(dir));
>
> ? ? ? ?addr = __dma_map_single(dev, cpu_addr, size, dir);
> + ? ? ? __dma_sync();
Russell,
I'm curious about the correctness of this patch for systems with
outer cache. shouldn't the dsb be issued before the outer cache
maintenance?
saeed
next prev parent reply other threads:[~2011-06-27 10:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 21:17 [PATCH v6 00/11] mmc: use nonblock mmc requests to minimize latency Per Forlin
2011-06-19 21:17 ` [PATCH v6 01/11] mmc: add non-blocking mmc request function Per Forlin
2011-06-19 21:17 ` [PATCH v6 02/11] omap_hsmmc: add support for pre_req and post_req Per Forlin
2011-06-21 5:41 ` Kishore Kadiyala
2011-06-21 6:51 ` Per Forlin
2011-06-21 13:56 ` Kishore Kadiyala
2011-06-21 19:18 ` Nicolas Pitre
2011-06-21 20:18 ` Per Forlin
2011-06-21 20:29 ` Nicolas Pitre
2011-06-19 21:17 ` [PATCH v6 03/11] mmci: implement pre_req() and post_req() Per Forlin
2011-06-19 21:17 ` [PATCH v6 04/11] mmc: mmc_test: add debugfs file to list all tests Per Forlin
2011-06-19 21:17 ` [PATCH v6 05/11] mmc: mmc_test: add test for non-blocking transfers Per Forlin
2011-06-19 21:17 ` [PATCH v6 06/11] mmc: add member in mmc queue struct to hold request data Per Forlin
2011-06-19 21:17 ` [PATCH v6 07/11] mmc: add a block request prepare function Per Forlin
2011-06-19 21:17 ` [PATCH v6 08/11] mmc: move error code in mmc_block_issue_rw_rq to a separate function Per Forlin
2011-06-19 21:17 ` [PATCH v6 09/11] mmc: add a second mmc queue request member Per Forlin
2011-06-19 21:17 ` [PATCH v6 10/11] mmc: test: add random fault injection in core.c Per Forlin
2011-06-19 21:17 ` [PATCH v6 11/11] mmc: add handling for two parallel block requests in issue_rw_rq Per Forlin
2011-06-20 15:17 ` Kishore Kadiyala
2011-06-21 6:40 ` Per Forlin
2011-06-21 7:05 ` Per Forlin
2011-06-21 13:52 ` Kishore Kadiyala
2011-06-21 21:01 ` Per Forlin
2011-06-21 7:14 ` Per Forlin
2011-06-21 7:53 ` [PATCH v6 00/11] mmc: use nonblock mmc requests to minimize latency Russell King - ARM Linux
2011-06-21 8:09 ` Per Forlin
2011-06-21 9:26 ` Per Forlin
2011-06-23 13:37 ` Russell King - ARM Linux
2011-06-24 8:58 ` Per Forlin
2011-06-27 9:42 ` Per Forlin
2011-06-27 10:02 ` Russell King - ARM Linux
2011-06-27 10:21 ` Per Forlin
2011-06-27 15:29 ` Linus Walleij
2011-06-27 16:34 ` Vijaya Kumar K-1
2011-06-27 10:34 ` saeed bishara [this message]
2011-06-27 11:02 ` Russell King - ARM Linux
2011-06-28 6:22 ` saeed bishara
2011-07-03 14:47 ` Russell King - ARM Linux
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=BANLkTimnuEK_9RedmD1OgcunX3rPvd-O0Q@mail.gmail.com \
--to=saeed.bishara@gmail.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 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).