From: Vladimir Murzin <vladimir.murzin@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: kbuild-all@01.org, linux@armlinux.org.uk, robin.murphy@arm.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [PATCH 6/7] ARM: NOMMU: Set ARM_DMA_MEM_BUFFERABLE for M-class cpus
Date: Wed, 15 Feb 2017 09:59:51 +0000 [thread overview]
Message-ID: <1487152792-34214-7-git-send-email-vladimir.murzin@arm.com> (raw)
In-Reply-To: <1487152792-34214-1-git-send-email-vladimir.murzin@arm.com>
Now, we have dedicated non-cacheable region for consistent DMA
operations. However, that region can still be marked as bufferable by
MPU, so it'd be safer to have barriers by default.
Tested-by: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Tested-by: Andras Szemzo <sza@esh.hu>
Tested-by: Alexandre TORGUE <alexandre.torgue@st.com>
Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
---
arch/arm/mm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig
index 0b79f12..64a1465c 100644
--- a/arch/arm/mm/Kconfig
+++ b/arch/arm/mm/Kconfig
@@ -1029,7 +1029,7 @@ config ARM_L1_CACHE_SHIFT
config ARM_DMA_MEM_BUFFERABLE
bool "Use non-cacheable memory for DMA" if (CPU_V6 || CPU_V6K) && !CPU_V7
- default y if CPU_V6 || CPU_V6K || CPU_V7
+ default y if CPU_V6 || CPU_V6K || CPU_V7 || CPU_V7M
help
Historically, the kernel has used strongly ordered mappings to
provide DMA coherent memory. With the advent of ARMv7, mapping
--
2.0.0
next prev parent reply other threads:[~2017-02-15 10:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 9:59 [PATCH 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU Vladimir Murzin
2017-02-15 9:59 ` [PATCH 1/7] dma: Take into account dma_pfn_offset Vladimir Murzin
2017-02-21 13:07 ` Robin Murphy
2017-02-21 13:20 ` Vladimir Murzin
2017-02-15 9:59 ` [PATCH 2/7] dma: Add simple dma_noop_mmap Vladimir Murzin
2017-02-15 9:59 ` [PATCH 3/7] drivers: dma-coherent: Account dma_pfn_offset when used with device tree Vladimir Murzin
2017-02-21 12:37 ` Robin Murphy
2017-02-21 13:02 ` Vladimir Murzin
2017-02-21 13:05 ` Vladimir Murzin
2017-02-21 17:11 ` Robin Murphy
2017-02-15 9:59 ` [PATCH 4/7] drivers: dma-coherent: Introduce default DMA pool Vladimir Murzin
2017-02-15 9:59 ` [PATCH 5/7] ARM: NOMMU: Introduce dma operations for noMMU Vladimir Murzin
2017-02-15 9:59 ` Vladimir Murzin [this message]
2017-02-21 12:57 ` [PATCH 6/7] ARM: NOMMU: Set ARM_DMA_MEM_BUFFERABLE for M-class cpus Robin Murphy
2017-02-21 13:03 ` Vladimir Murzin
2017-02-15 9:59 ` [PATCH 7/7] ARM: dma-mapping: Remove traces of NOMMU code Vladimir Murzin
2017-02-21 10:41 ` [PATCH 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU Vladimir Murzin
2017-02-21 12:16 ` Robin Murphy
2017-02-21 12:27 ` Vladimir Murzin
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=1487152792-34214-7-git-send-email-vladimir.murzin@arm.com \
--to=vladimir.murzin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robin.murphy@arm.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®