From: Rob Clark <robdclark@gmail.com>
To: iommu@lists.linux-foundation.org, linux-arm-msm@vger.kernel.org,
Will Deacon <will.deacon@arm.com>,
Sricharan R <sricharan@codeaurora.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Rob Clark <robdclark@gmail.com>
Subject: [RFC 0/3] iommu/arm-smmu: stalling support (v2)
Date: Wed, 1 Feb 2017 10:23:38 -0500 [thread overview]
Message-ID: <20170201152341.29142-1-robdclark@gmail.com> (raw)
Now, as was previously discussed[1], now we have a dt property on the
smmu, to indicate that the smmu supports stalling, as well as a flag
on the domain (set when fault-handler is registered) to indicate that
the domain supports stalling.
I ran into one snag, thanks to the auto-attached DMA domain, since
that doesn't support stalling. I think when the driver is explicitly
managing the iommu, we should just get rid of the DMA domain. (But
maybe there is a cleaner way to do this than what I came up with, so
suggestions welcome.)
[1] http://www.spinics.net/lists/linux-arm-msm/msg25357.html
Rob Clark (3):
iommu: introduce stall/resume support
iommu/arm-smmu: Add support to opt-in to stalling
iommu/arm-smmu: detach DMA domain if driver is managing iommu
.../devicetree/bindings/iommu/arm,smmu.txt | 3 +
drivers/gpu/drm/etnaviv/etnaviv_mmu.c | 2 +-
drivers/gpu/drm/msm/msm_iommu.c | 12 ++-
drivers/infiniband/hw/usnic/usnic_uiom.c | 2 +-
drivers/iommu/arm-smmu.c | 100 +++++++++++++++++++--
drivers/iommu/iommu.c | 24 ++++-
drivers/remoteproc/remoteproc_core.c | 2 +-
include/linux/iommu.h | 5 +-
8 files changed, 136 insertions(+), 14 deletions(-)
--
2.9.3
next reply other threads:[~2017-02-01 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 15:23 Rob Clark [this message]
[not found] ` <20170201152341.29142-1-robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-01 15:23 ` [RFC 1/3] iommu: introduce stall/resume support Rob Clark
2017-02-01 15:23 ` [RFC 2/3] iommu/arm-smmu: Add support to opt-in to stalling Rob Clark
2017-02-01 15:23 ` [RFC 3/3] iommu/arm-smmu: detach DMA domain if driver is managing iommu Rob Clark
[not found] ` <20170201152341.29142-4-robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-01 15:30 ` Rob Clark
[not found] ` <CAF6AEGvXc1dUaqQ6=yp9XCZTv6y1r7jNJohrksO0=EJ1+UFY5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-02 4:10 ` Sricharan
2017-02-02 12:14 ` Rob Clark
2017-02-02 16:20 ` Rob Clark
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=20170201152341.29142-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jcrouse@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sricharan@codeaurora.org \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.