From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Introduce interface for default DMA pool
Date: Thu, 20 Jul 2017 11:19:57 +0100 [thread overview]
Message-ID: <1500545999-17177-1-git-send-email-vladimir.murzin@arm.com> (raw)
Hi,
This is follow-up for Christoph complain [1] of overloading the current
dma coherent infrastructure with the global pool. To address that I
implemented Robin's idea of the new interface to the global pool and
wire up it with (only existent user) ARM NOMMU. Since I have not
heard from Vitaly and/or George of their use of global pool, I'm
leaving ARM MMU part to them.
Changelog:
RFC -> v1
- dropped RFC tag
- s/_from_coherent/_from_dev_coherent/g per Christoph
- added Tested-by from Andras
[1] https://lkml.org/lkml/2017/7/7/370
Cc: Vineet Gupta <vgupta@synopsys.com>
Cc: Russell King <linux@armlinux.org.uk>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Thanks!
Vladimir Murzin (2):
drivers: dma-coherent: Introduce interface for default DMA pool
ARM: NOMMU: Wire-up default DMA interface
arch/arc/mm/dma.c | 2 +-
arch/arm/mm/dma-mapping-nommu.c | 45 ++++++++---
arch/arm/mm/dma-mapping.c | 2 +-
arch/arm64/mm/dma-mapping.c | 4 +-
arch/mips/mm/dma-default.c | 2 +-
drivers/base/dma-coherent.c | 169 ++++++++++++++++++++++++++--------------
drivers/base/dma-mapping.c | 2 +-
include/linux/dma-mapping.h | 40 ++++++++--
8 files changed, 185 insertions(+), 81 deletions(-)
--
2.0.0
next reply other threads:[~2017-07-20 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 10:19 Vladimir Murzin [this message]
2017-07-20 10:19 ` [PATCH 1/2] drivers: dma-coherent: Introduce interface for default DMA pool Vladimir Murzin
2017-07-20 13:45 ` Robin Murphy
2017-07-20 14:11 ` Christoph Hellwig
2017-07-20 10:19 ` [PATCH 2/2] ARM: NOMMU: Wire-up default DMA interface Vladimir Murzin
2017-07-20 13:48 ` Robin Murphy
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=1500545999-17177-1-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;
as well as URLs for NNTP newsgroup(s).