From: Will Deacon <will@kernel.org>
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
Sibi Sankar <sibis@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
Rob Clark <robdclark@gmail.com>,
jroedel@suse.de, Stephen Boyd <swboyd@chromium.org>,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Matthias Kaehlcke <mka@chromium.org>,
Evan Green <evgreen@chromium.org>,
linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCHv4 0/6] iommu/arm-smmu: Allow client devices to select identity mapping
Date: Thu, 7 May 2020 11:31:29 +0100 [thread overview]
Message-ID: <20200507103129.GA29541@willie-the-truck> (raw)
In-Reply-To: <aa54fd00a6d353c72664e41b7a4a4e3d@codeaurora.org>
On Thu, May 07, 2020 at 03:58:06PM +0530, Sai Prakash Ranjan wrote:
> Hi Will, Joerg
>
> On 2020-04-21 00:03, Sai Prakash Ranjan wrote:
> > This series allows DRM, Modem devices to set a default
> > identity mapping in qcom smmu implementation.
> >
> > Patch 1 is cleanup to support other SoCs to call into
> > QCOM specific implementation.
> > Patch 2 sets the default identity domain for DRM devices.
> > Patch 3 implements def_domain_type callback for arm-smmu.
> > Patch 4 sets the default identity domain for modem device.
> > Patch 5-6 adds the iommus property for mss pil.
> >
> > This is based on Joerg's tree:
> > -
> > https://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git/log/?h=iommu-probe-device-v2
> >
> > v4:
> > * Updated commit msg for mss pil requesting direct mapping
> >
> > v3:
> > * Use arm_smmu_master_cfg to get impl instead of long way as per Robin.
> > * Use def_domain_type name for the callback in arm_smmu_imp as per
> > Robin
> >
> > Jordan Crouse (1):
> > iommu/arm-smmu: Allow client devices to select direct mapping
> >
> > Sai Prakash Ranjan (2):
> > iommu: arm-smmu-impl: Convert to a generic reset implementation
> > iommu/arm-smmu: Implement iommu_ops->def_domain_type call-back
> >
> > Sibi Sankar (3):
> > iommu/arm-smmu-qcom: Request direct mapping for modem device
> > dt-bindings: remoteproc: qcom: Add iommus property
> > arm64: dts: qcom: sdm845-cheza: Add iommus property
> >
> > .../bindings/remoteproc/qcom,q6v5.txt | 3 ++
> > arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 5 +++
> > drivers/iommu/arm-smmu-impl.c | 8 ++--
> > drivers/iommu/arm-smmu-qcom.c | 37 +++++++++++++++++--
> > drivers/iommu/arm-smmu.c | 12 ++++++
> > drivers/iommu/arm-smmu.h | 1 +
> > 6 files changed, 60 insertions(+), 6 deletions(-)
>
> This series is reviewed by Robin.
> Any chance this series can make it to 5.8?
I'm planning to queue smmu stuff next week, been busy with arm64 stuff
so far, sorry.
Will
next prev parent reply other threads:[~2020-05-07 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 18:33 [PATCHv4 0/6] iommu/arm-smmu: Allow client devices to select identity mapping Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 1/6] iommu: arm-smmu-impl: Convert to a generic reset implementation Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 2/6] iommu/arm-smmu: Implement iommu_ops->def_domain_type call-back Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 3/6] iommu/arm-smmu: Allow client devices to select direct mapping Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 4/6] iommu/arm-smmu-qcom: Request direct mapping for modem device Sai Prakash Ranjan
2020-05-07 13:02 ` Will Deacon
2020-05-07 14:14 ` Sibi Sankar
2020-05-07 14:18 ` Will Deacon
2020-04-20 18:33 ` [PATCHv4 5/6] dt-bindings: remoteproc: qcom: Add iommus property Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 6/6] arm64: dts: qcom: sdm845-cheza: " Sai Prakash Ranjan
2020-05-07 10:28 ` [PATCHv4 0/6] iommu/arm-smmu: Allow client devices to select identity mapping Sai Prakash Ranjan
2020-05-07 10:31 ` Will Deacon [this message]
2020-05-07 11:08 ` Sai Prakash Ranjan
2020-05-07 14:04 ` Will Deacon
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=20200507103129.GA29541@willie-the-truck \
--to=will@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=evgreen@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jcrouse@codeaurora.org \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=sibis@codeaurora.org \
--cc=swboyd@chromium.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).