From: Thierry Reding <thierry.reding@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
Nicolin Chen <nicoleotsuka@gmail.com>,
inux-mmc@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] mmc: tegra: Use proper DMA mask
Date: Fri, 20 Sep 2019 16:53:15 +0200 [thread overview]
Message-ID: <20190920145317.11972-1-thierry.reding@gmail.com> (raw)
From: Thierry Reding <treding@nvidia.com>
Hi,
this puts together the two patches from this thread:
http://patchwork.ozlabs.org/patch/1146705/
there hasn't been any activity there for a couple of weeks, so I thought
I'd just throw them together and update the second patch to work on top
of the first one.
The goal here is to avoid the use of bounce buffers and fix IOVA space
issues when an IOMMU gets involved. The first patch introduces the
->set_dma_mask() host operation as proposed by Adrian and the second
patch is just a rebase of Nicolin's Tegra SDHCI patch that uses the new
host operation rather than doing it as part of ->enable_dma().
Thierry
Adrian Hunter (1):
mmc: sdhci: Let drivers define their DMA mask
Nicolin Chen (1):
mmc: tegra: Implement ->set_dma_mask()
drivers/mmc/host/sdhci-tegra.c | 48 ++++++++++++++++++++--------------
drivers/mmc/host/sdhci.c | 12 +++------
drivers/mmc/host/sdhci.h | 1 +
3 files changed, 33 insertions(+), 28 deletions(-)
--
2.23.0
next reply other threads:[~2019-09-20 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 14:53 Thierry Reding [this message]
2019-09-20 14:53 ` [PATCH 1/2] mmc: sdhci: Let drivers define their DMA mask Thierry Reding
2019-09-20 21:47 ` Nicolin Chen
2019-09-20 14:53 ` [PATCH 2/2] mmc: tegra: Implement ->set_dma_mask() Thierry Reding
2019-09-23 6:39 ` Adrian Hunter
2019-09-23 6:41 ` Adrian Hunter
2019-09-20 16:17 ` [PATCH 0/2] mmc: tegra: Use proper DMA mask Thierry Reding
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=20190920145317.11972-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=inux-mmc@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=ulf.hansson@linaro.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).