From: Eli Billauer <eli.billauer@gmail.com>
To: tj@kernel.org
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
bhelgaas@google.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, shuah.kh@samsung.com,
iommu@lists.linux-foundation.org, discuss@x86-64.org,
Eli Billauer <eli.billauer@gmail.com>
Subject: [PATCH v2 0/4] devres: dma-mapping: Introducing new functions
Date: Sun, 1 Jun 2014 10:01:13 +0300 [thread overview]
Message-ID: <1401606077-1739-1-git-send-email-eli.billauer@gmail.com> (raw)
This patchset consists of new functions to the managed device resource
API, followed by a patch for the Xillybus driver, which is my motivation
and what I tested with.
This is a resubmission after changing the API slightly.
Rationale: While migrating the staging/xillybus driver to rely completely on
managed resources, some functionalities were missing, and hence added:
* dmam_map_single()
* dmam_unmap_single()
* pcim_map_single()
* pcim_unmap_single()
Tejun suggested that dma_map_single_attrs() should have a managed version as
well. The second patch in this set turns dmam_map_single() into
dma_map_single_attrs(), and implements the former as a macro. Functions added:
* dmam_map_single_attrs()
* dmam_unmap_single_attrs()
Xillybus' driver works with and without this patch (depends on patches #1 and #3
only).
Thanks,
Eli
Eli Billauer (4):
dma-mapping: Add devm_ interface for dma_map_single()
dma-mapping: Add devm_ interface for dma_map_single_attrs()
dma-mapping: pci: Add devm_ interface for pci_map_single
staging: xillybus: Use devm_ API for memory allocation and DMA
mapping
Documentation/driver-model/devres.txt | 6 +
drivers/base/dma-mapping.c | 106 +++++++++++++++++
drivers/staging/xillybus/xillybus.h | 38 +------
drivers/staging/xillybus/xillybus_core.c | 186 +++++++++---------------------
drivers/staging/xillybus/xillybus_of.c | 61 +---------
drivers/staging/xillybus/xillybus_pcie.c | 54 ++--------
include/asm-generic/dma-mapping-common.h | 3 +
include/asm-generic/pci-dma-compat.h | 18 +++
include/linux/dma-mapping.h | 8 +-
9 files changed, 214 insertions(+), 266 deletions(-)
--
1.7.2.3
next reply other threads:[~2014-06-01 7:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 7:01 Eli Billauer [this message]
2014-06-01 7:01 ` [PATCH v2 1/4] dma-mapping: Add devm_ interface for dma_map_single() Eli Billauer
2014-06-03 21:24 ` Shuah Khan
2014-06-03 23:39 ` Joerg Roedel
2014-06-04 14:04 ` Tejun Heo
2014-06-04 14:12 ` Joerg Roedel
2014-06-04 14:14 ` Tejun Heo
2014-06-04 15:03 ` Eli Billauer
2014-06-04 21:25 ` Joerg Roedel
2014-06-06 11:45 ` Eli Billauer
2014-06-06 16:01 ` Greg KH
2014-06-06 16:21 ` Eli Billauer
2014-06-06 17:02 ` Shuah Khan
2014-06-07 11:23 ` Eli Billauer
2014-06-01 7:01 ` [PATCH v2 2/4] dma-mapping: Add devm_ interface for dma_map_single_attrs() Eli Billauer
2014-06-01 7:01 ` [PATCH v2 3/4] dma-mapping: pci: Add devm_ interface for pci_map_single Eli Billauer
2014-06-01 7:01 ` [PATCH v2 4/4] staging: xillybus: Use devm_ API for memory allocation and DMA mapping Eli Billauer
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=1401606077-1739-1-git-send-email-eli.billauer@gmail.com \
--to=eli.billauer@gmail.com \
--cc=bhelgaas@google.com \
--cc=devel@driverdev.osuosl.org \
--cc=discuss@x86-64.org \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=shuah.kh@samsung.com \
--cc=tj@kernel.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).