Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v4 4/5] ARM: NOMMU: Set ARM_DMA_MEM_BUFFERABLE for M-class cpus
Date: Tue, 10 Jan 2017 14:18:44 +0000	[thread overview]
Message-ID: <1484057925-23586-5-git-send-email-vladimir.murzin@arm.com> (raw)
In-Reply-To: <1484057925-23586-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.

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

  parent reply	other threads:[~2017-01-10 14:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 14:18 [RFC PATCH v4 0/5] ARM: Fix dma_alloc_coherent() and friends for NOMMU Vladimir Murzin
2017-01-10 14:18 ` [RFC PATCH v4 1/5] dma: Add simple dma_noop_mmap Vladimir Murzin
2017-01-10 14:18 ` [RFC PATCH v4 2/5] drivers: dma-coherent: Introduce default DMA pool Vladimir Murzin
2017-01-10 14:18 ` [RFC PATCH v4 3/5] ARM: NOMMU: Introduce dma operations for noMMU Vladimir Murzin
2017-01-10 14:18 ` Vladimir Murzin [this message]
2017-01-10 14:18 ` [RFC PATCH v4 5/5] ARM: dma-mapping: Remove traces of NOMMU code Vladimir Murzin
2017-01-11 13:17 ` [RFC PATCH v4 0/5] ARM: Fix dma_alloc_coherent() and friends for NOMMU Benjamin Gaignard
2017-01-11 14:34   ` Vladimir Murzin
2017-01-12 10:35     ` Benjamin Gaignard
2017-01-12 10:55       ` Benjamin Gaignard
2017-01-12 16:52         ` Vladimir Murzin
2017-01-12 17:04           ` Robin Murphy
2017-01-12 17:15             ` Vladimir Murzin
2017-01-12 18:07               ` Robin Murphy
2017-01-13  9:12                 ` Vladimir Murzin
2017-01-13 12:40                   ` Robin Murphy
2017-01-16 11:58                     ` 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=1484057925-23586-5-git-send-email-vladimir.murzin@arm.com \
    --to=vladimir.murzin@arm.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