From: Will Deacon <will@kernel.org>
To: Jordan Crouse <jcrouse@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
freedreno@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] iommu/arm-smmu: Add a init_context_bank implementation hook
Date: Mon, 13 Jul 2020 16:11:23 +0100 [thread overview]
Message-ID: <20200713151123.GB3072@willie-the-truck> (raw)
In-Reply-To: <20200611223656.4724-1-jcrouse@codeaurora.org>
On Thu, Jun 11, 2020 at 04:36:56PM -0600, Jordan Crouse wrote:
> Add a new implementation hook to allow the implementation specific code
> to tweek the context bank configuration just before it gets written.
> The first user will be the Adreno GPU implementation to turn on
> SCTLR.HUPCF to ensure that a page fault doesn't terminating pending
> transactions. Doing so could hang the GPU if one of the terminated
> transactions is a CP read.
>
> This depends on the arm-smmu adreno SMMU implementation [1].
>
> [1] https://patchwork.kernel.org/patch/11600943/
>
> Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
> ---
>
> drivers/iommu/arm-smmu-qcom.c | 13 +++++++++++++
> drivers/iommu/arm-smmu.c | 28 +++++++++++++---------------
> drivers/iommu/arm-smmu.h | 11 +++++++++++
> 3 files changed, 37 insertions(+), 15 deletions(-)
This looks straightforward enough, but I don't want to merge this without
a user and Sai's series has open questions afaict.
Will
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-07-13 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 22:36 [PATCH] iommu/arm-smmu: Add a init_context_bank implementation hook Jordan Crouse
2020-07-13 15:11 ` Will Deacon [this message]
2020-07-13 17:00 ` Jordan Crouse
2020-07-13 19:03 ` Will Deacon
2020-07-13 19:13 ` [Freedreno] " Jordan Crouse
2020-07-14 4:37 ` Sai Prakash Ranjan
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=20200713151123.GB3072@willie-the-truck \
--to=will@kernel.org \
--cc=freedreno@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jcrouse@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@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 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).