From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/2] ARM: dma-mapping: Don't use outer_flush_range when the L2C is coherent
Date: Thu, 7 Apr 2016 19:57:04 +0100 [thread overview]
Message-ID: <20160407185704.GH19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1459415380-18004-2-git-send-email-gregory.clement@free-electrons.com>
On Thu, Mar 31, 2016 at 11:09:39AM +0200, Gregory CLEMENT wrote:
> diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
> index deac58d5f1f7..1538bb293e90 100644
> --- a/arch/arm/mm/dma-mapping.c
> +++ b/arch/arm/mm/dma-mapping.c
> @@ -61,7 +61,7 @@ struct arm_dma_free_args {
>
> struct arm_dma_allocator {
> void *(*alloc)(struct arm_dma_alloc_args *args,
> - struct page **ret_page);
> + struct page **ret_page, bool is_coherent);
This should be named "l2_coherent" because it controls whether L2
cache flushing is done: L1 cache flushing calls are still present.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-04-07 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 9:09 [PATCH v6 0/2] Fix dma mapping when the cache is coherent Gregory CLEMENT
2016-03-31 9:09 ` [PATCH v6 1/2] ARM: dma-mapping: Don't use outer_flush_range when the L2C " Gregory CLEMENT
2016-04-07 18:57 ` Russell King - ARM Linux [this message]
2016-04-07 21:45 ` Gregory CLEMENT
2016-04-08 4:41 ` Rabin Vincent
2016-04-12 12:55 ` Gregory CLEMENT
2016-03-31 9:09 ` [PATCH v6 2/2] ARM: dma-mapping: Fix the coherent case when iommu is used Gregory CLEMENT
2016-04-01 13:01 ` [PATCH v6 0/2] Fix dma mapping when the cache is coherent Marcin Wojtas
2016-04-07 18:51 ` Gregory CLEMENT
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=20160407185704.GH19428@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).