From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: Default to non-coherent DMA ops
Date: Fri, 25 Apr 2014 18:34:11 +0100 [thread overview]
Message-ID: <1398447254-18527-1-git-send-email-catalin.marinas@arm.com> (raw)
Following recent discussions and patch from Ritesh, I'm planning to
align the default DMA ops with 32-bit arm and make them non-coherent. In
addition, we need to make sure that devices marked explicitly as
coherent use the correct dma ops. Until Santosh's DMA patches get
reviewed/merged, the temporary solution is bus notifiers which check the
"dma-coherent" property and set the right dma ops.
Catalin Marinas (2):
arm64: Use bus notifiers to set per-device coherent DMA ops
arm64: Mark the Applied Micro X-Gene SATA controller as DMA coherent
Ritesh Harjani (1):
arm64: Make default dma_ops to be noncoherent
.../devicetree/bindings/ata/apm-xgene.txt | 3 ++
arch/arm64/boot/dts/apm-storm.dtsi | 3 ++
arch/arm64/kernel/setup.c | 2 +-
arch/arm64/mm/dma-mapping.c | 35 ++++++++++++++++++++--
4 files changed, 40 insertions(+), 3 deletions(-)
next reply other threads:[~2014-04-25 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 17:34 Catalin Marinas [this message]
2014-04-25 17:34 ` [PATCH 1/3] arm64: Make default dma_ops to be noncoherent Catalin Marinas
2014-04-25 17:34 ` [PATCH 2/3] arm64: Use bus notifiers to set per-device coherent DMA ops Catalin Marinas
2014-04-25 17:34 ` [PATCH 3/3] arm64: Mark the Applied Micro X-Gene SATA controller as DMA coherent Catalin Marinas
2014-04-25 18:19 ` [PATCH 0/3] arm64: Default to non-coherent DMA ops Rob Herring
2014-04-26 9:38 ` Catalin Marinas
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=1398447254-18527-1-git-send-email-catalin.marinas@arm.com \
--to=catalin.marinas@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;
as well as URLs for NNTP newsgroup(s).