From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: kholk11@gmail.com
Cc: marijns95@gmail.com, linux-arm-msm@vger.kernel.org,
iommu@lists.linux-foundation.org, agross@kernel.org
Subject: Re: [PATCH v4 0/7] Add support for QCOM IOMMU v2 and 500
Date: Fri, 4 Oct 2019 21:56:26 -0700 [thread overview]
Message-ID: <20191005045626.GE6390@tuxbook-pro> (raw)
In-Reply-To: <20191001220205.6423-1-kholk11@gmail.com>
On Tue 01 Oct 15:01 PDT 2019, kholk11@gmail.com wrote:
> From: AngeloGioacchino Del Regno <kholk11@gmail.com>
>
> Some Qualcomm Family-B SoCs have got a different version of the QCOM
> IOMMU, specifically v2 and 500, which perfectly adhere to the current
> qcom_iommu driver, but need some variations due to slightly different
> hypervisor behavior.
>
Do you think it's out of the question to get the arm-smmu driver to play
nice with this platform?
If not, would it be possible to change the DT binding so that we specify
the SID and then read the SMR and S2CR registers to figure out the
associated context bank?
Regards,
Bjorn
> The personal aim is to upstream MSM8956 as much as possible.
>
> This code has been tested on two Sony phones featuring the Qualcomm
> MSM8956 SoC.
>
> Changes in v2:
> - Fixed optional properties placement in documentation
>
> Changes in v3:
> - Rebased onto linux-next 01/10/2019
> - Added missing SCM commit (required by the AArch64 PT switch support)
>
> Changes in v4:
> - Removed rej files from the SCM patch (I'm truly sorry for the noise...)
>
> Angelo G. Del Regno (1):
> firmware: qcom: scm: Add function to set IOMMU pagetable addressing
>
> AngeloGioacchino Del Regno (6):
> iommu/qcom: Use the asid read from device-tree if specified
> iommu/qcom: Write TCR before TTBRs to fix ASID access behavior
> iommu/qcom: Properly reset the IOMMU context
> iommu/qcom: Add support for AArch64 IOMMU pagetables
> iommu/qcom: Index contexts by asid number to allow asid 0
> iommu/qcom: Add support for QCIOMMUv2 and QCIOMMU-500 secured contexts
>
> .../devicetree/bindings/iommu/qcom,iommu.txt | 5 +
> drivers/firmware/qcom_scm-32.c | 6 +
> drivers/firmware/qcom_scm-64.c | 15 ++
> drivers/firmware/qcom_scm.c | 7 +
> drivers/firmware/qcom_scm.h | 4 +
> drivers/iommu/qcom_iommu.c | 134 ++++++++++++++----
> include/linux/qcom_scm.h | 2 +
> 7 files changed, 145 insertions(+), 28 deletions(-)
>
> --
> 2.21.0
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-10-05 4:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 22:01 [PATCH v4 0/7] Add support for QCOM IOMMU v2 and 500 kholk11
2019-10-01 22:01 ` [PATCH v4 1/7] firmware: qcom: scm: Add function to set IOMMU pagetable addressing kholk11
2019-10-15 11:14 ` Joerg Roedel
2019-10-15 12:33 ` AngeloGioacchino Del Regno
2019-10-15 12:40 ` Joerg Roedel
2019-10-15 13:09 ` AngeloGioacchino Del Regno
2019-10-01 22:02 ` [PATCH v4 2/7] iommu/qcom: Use the asid read from device-tree if specified kholk11
2019-10-15 12:09 ` Robin Murphy
2019-10-15 13:06 ` AngeloGioacchino Del Regno
2019-10-01 22:02 ` [PATCH v4 3/7] iommu/qcom: Write TCR before TTBRs to fix ASID access behavior kholk11
2019-10-01 22:02 ` [PATCH v4 4/7] iommu/qcom: Properly reset the IOMMU context kholk11
2019-10-02 11:29 ` Robin Murphy
2019-10-01 22:02 ` [PATCH v4 5/7] iommu/qcom: Add support for AArch64 IOMMU pagetables kholk11
2019-10-01 22:02 ` [PATCH v4 6/7] iommu/qcom: Index contexts by asid number to allow asid 0 kholk11
2019-10-01 22:02 ` [PATCH v4 7/7] iommu/qcom: Add support for QCIOMMUv2 and QCIOMMU-500 secured contexts kholk11
2019-10-05 4:56 ` Bjorn Andersson [this message]
2019-10-05 9:32 ` [PATCH v4 0/7] Add support for QCOM IOMMU v2 and 500 AngeloGioacchino Del Regno
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=20191005045626.GE6390@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kholk11@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marijns95@gmail.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