From: ritesh.harjani@gmail.com (Ritesh Harjani)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Make default dma_ops to be noncoherent
Date: Wed, 23 Apr 2014 10:59:46 +0530 [thread overview]
Message-ID: <1398230986-2823-2-git-send-email-ritesh.harjani@gmail.com> (raw)
In-Reply-To: <1398230986-2823-1-git-send-email-ritesh.harjani@gmail.com>
Currently arm64 dma_ops is by default made coherent
which makes it opposite in default policy
from arm.
Make default dma_ops to be noncoherent (same
as arm), as currently there aren't any
dma-capable drivers which assumes coherent ops
Signed-off-by: Ritesh Harjani <ritesh.harjani@gmail.com>
---
arch/arm64/mm/dma-mapping.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/mm/dma-mapping.c b/arch/arm64/mm/dma-mapping.c
index 0ba347e..1f65963 100644
--- a/arch/arm64/mm/dma-mapping.c
+++ b/arch/arm64/mm/dma-mapping.c
@@ -311,7 +311,7 @@ static int __init swiotlb_late_init(void)
{
size_t swiotlb_size = min(SZ_64M, MAX_ORDER_NR_PAGES << PAGE_SHIFT);
- dma_ops = &coherent_swiotlb_dma_ops;
+ dma_ops = &noncoherent_swiotlb_dma_ops;
return swiotlb_late_init_with_default_size(swiotlb_size);
}
--
1.8.1.3
next prev parent reply other threads:[~2014-04-23 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 12:48 arm64: default dma_ops is set to coherent_dma_ops results into DMA FAILURE Ritesh Harjani
2014-04-22 13:20 ` Will Deacon
2014-04-22 14:04 ` Catalin Marinas
2014-04-22 15:21 ` Will Deacon
2014-04-23 5:29 ` Ritesh Harjani
2014-04-23 5:29 ` Ritesh Harjani [this message]
2014-04-23 9:05 ` [PATCH] arm64: Make default dma_ops to be noncoherent Will Deacon
2014-04-23 10:00 ` Ritesh Harjani
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=1398230986-2823-2-git-send-email-ritesh.harjani@gmail.com \
--to=ritesh.harjani@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).