From: Vladimir Murzin <vladimir.murzin@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux@armlinux.org.uk, sza@esh.hu,
arnd@arndb.de, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, alexandre.torgue@st.com,
robin.murphy@arm.com, kbuild-all@01.org,
benjamin.gaignard@linaro.org, hch@lst.de,
m.szyprowski@samsung.com, vitaly_kuzmichev@mentor.com,
george_davis@mentor.com
Subject: [RFC PATCH 0/2] Introduce interface for default DMA pool
Date: Mon, 17 Jul 2017 09:58:03 +0100 [thread overview]
Message-ID: <1500281885-3034-1-git-send-email-vladimir.murzin@arm.com> (raw)
Hi,
This is follow-up for Christoph complain 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.
[1] https://lkml.org/lkml/2017/7/7/370
Vladimir Murzin (2):
drivers: dma-coherent: Introduce interface for default DMA pool
ARM: NOMMU: Wire-up default DMA interface
arch/arm/mm/dma-mapping-nommu.c | 45 +++++++++---
drivers/base/dma-coherent.c | 159 ++++++++++++++++++++++++++--------------
include/linux/dma-mapping.h | 24 ++++++
3 files changed, 166 insertions(+), 62 deletions(-)
--
2.0.0
next reply other threads:[~2017-07-17 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 8:58 Vladimir Murzin [this message]
2017-07-17 8:58 ` [RFC PATCH 1/2] drivers: dma-coherent: " Vladimir Murzin
2017-07-19 7:20 ` Christoph Hellwig
2017-07-17 8:58 ` [RFC PATCH 2/2] ARM: NOMMU: Wire-up default DMA interface Vladimir Murzin
2017-07-19 7:21 ` Christoph Hellwig
2017-07-20 9:29 ` [RFC PATCH 0/2] Introduce interface for default DMA pool Szemző András
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=1500281885-3034-1-git-send-email-vladimir.murzin@arm.com \
--to=vladimir.murzin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@linaro.org \
--cc=george_davis@mentor.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=sza@esh.hu \
--cc=vitaly_kuzmichev@mentor.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®