Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932411AbdGCOvp (ORCPT ); Mon, 3 Jul 2017 10:51:45 -0400 Received: from relay1.mentorg.com ([192.94.38.131]:33203 "EHLO relay1.mentorg.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932200AbdGCOv0 (ORCPT ); Mon, 3 Jul 2017 10:51:26 -0400 From: To: CC: , , , , , , Vitaly Kuzmichev Subject: [PATCH 0/2] Implement default DMA coherent pool Date: Mon, 3 Jul 2017 17:51:13 +0300 Message-ID: <1499093475-29859-1-git-send-email-vitaly_kuzmichev@mentor.com> X-Mailer: git-send-email 1.9.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [137.202.0.87] X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To SVR-IES-MBX-03.mgc.mentorg.com (139.181.222.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1103 Lines: 31 From: Vitaly Kuzmichev 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