[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1499093475-29859-1-git-send-email-vitaly_kuzmichev@mentor.com>
Date: Mon, 3 Jul 2017 17:51:13 +0300
From: <vitaly_kuzmichev@...tor.com>
To: <gregkh@...uxfoundation.org>
CC: <mark.rutland@....com>, <robh+dt@...nel.org>,
<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<george_davis@...tor.com>, <vitaly_kuzmichev@...tor.com>,
Vitaly Kuzmichev <Vitaly_Kuzmichev@...tor.com>
Subject: [PATCH 0/2] Implement default DMA coherent pool
From: Vitaly Kuzmichev <Vitaly_Kuzmichev@...tor.com>
Here is alternate version to implement default DMA coherent pool, that
we use in our custom kernel since 2015.
Unlike to Vladimir Murzin's patch [1] "drivers: dma-coherent: Introduce
default DMA pool" this variant stores pointer to "rmem->priv" pointer
and thus it does not need additional function (dma_init_reserved_memory)
to explicitly call device_init (=rmem_dma_device_init) to get valid
address in "rmem->priv".
Default DMA pool attribute for memory region is being provided from
a device tree file.
Patch 2/2 adds 'dmainfo' to ProcFS to show available DMA regions.
The patchset is based on driver-core-next branch.
[1] https://patchwork.kernel.org/patch/9615465/
George G. Davis (2):
drivers: dma-coherent: Add support for default DMA coherent pool
drivers: dma-coherent: show per-device DMA region utilization via
procfs
.../bindings/reserved-memory/reserved-memory.txt | 2 +
drivers/base/dma-coherent.c | 250 +++++++++++++++++++--
2 files changed, 237 insertions(+), 15 deletions(-)
--
1.9.1
Powered by blists - more mailing lists