From: Sibi Sankar <sibis@codeaurora.org>
To: bjorn.andersson@linaro.org, robh+dt@kernel.org, joro@8bytes.org,
robin.murphy@arm.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-remoteproc@vger.kernel.org, ohad@wizery.com,
agross@kernel.org, dianders@chromium.org,
saiprakash.ranjan@codeaurora.org
Subject: Re: [PATCH v2 0/3] Request direct mapping for modem device
Date: Tue, 17 Mar 2020 21:22:21 +0530 [thread overview]
Message-ID: <fe9bb128563bea9798573ac9eec1d214@codeaurora.org> (raw)
In-Reply-To: <20200317150910.26053-1-sibis@codeaurora.org>
On 2020-03-17 20:39, Sibi Sankar wrote:
> The Q6 modem sub-system has direct access to DDR through memnoc and
> an indirect access routed through a SMMU which MSS CE (crypto engine
> sub-component of MSS) uses during out of reset sequence. Request direct
> mapping for the modem device since smmu is not expected to provide
> access
> control/translation for these SIDs (sandboxing of the modem is achieved
> through XPUs engaged using SMC calls). This is done on platforms which
> don't have TrustZone (which programs the modem SIDs) to prevent the
> following global faults seen on Cheza/Trogdor:
>
> Cheza:
> arm-smmu 15000000.iommu: Unexpected global fault, this could be serious
> arm-smmu 15000000.iommu: GFSR 0x80000002, GFSYNR0 0x00000000,
> GFSYNR1 0x00000781, GFSYNR2 0x00000000
>
> Trogdor:
> arm-smmu 15000000.iommu: Unexpected global fault, this could be serious
> arm-smmu 15000000.iommu: GFSR 0x80000002, GFSYNR0 0x00000000,
> GFSYNR1 0x00000461, GFSYNR2 0x00000000
>
> V2:
> * Request direct mapping from SoC-specific corner of the SMMU
> driver [Robin]
> * Add iommu property to remoteproc modem node on Cheza
>
> Depends on:
> https://lore.kernel.org/patchwork/cover/1183528/
>
> Sibi Sankar (3):
> dt-bindings: remoteproc: qcom: Add iommus property
> remoteproc: qcom_q6v5_mss: Request direct mapping for modem device
iommu: arm-smmu-qcom: Request direct mapping for modem device
sry should have been ^^ instead
> arm64: dts: qcom: sdm845-cheza: Add iommus property
>
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 3 +++
> arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 4 ++++
> drivers/iommu/arm-smmu-qcom.c | 6 ++++++
> 3 files changed, 13 insertions(+)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
WARNING: multiple messages have this Message-ID (diff)
From: Sibi Sankar <sibis@codeaurora.org>
To: bjorn.andersson@linaro.org, robh+dt@kernel.org, joro@8bytes.org,
robin.murphy@arm.com
Cc: ohad@wizery.com, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, dianders@chromium.org,
iommu@lists.linux-foundation.org, agross@kernel.org
Subject: Re: [PATCH v2 0/3] Request direct mapping for modem device
Date: Tue, 17 Mar 2020 21:22:21 +0530 [thread overview]
Message-ID: <fe9bb128563bea9798573ac9eec1d214@codeaurora.org> (raw)
In-Reply-To: <20200317150910.26053-1-sibis@codeaurora.org>
On 2020-03-17 20:39, Sibi Sankar wrote:
> The Q6 modem sub-system has direct access to DDR through memnoc and
> an indirect access routed through a SMMU which MSS CE (crypto engine
> sub-component of MSS) uses during out of reset sequence. Request direct
> mapping for the modem device since smmu is not expected to provide
> access
> control/translation for these SIDs (sandboxing of the modem is achieved
> through XPUs engaged using SMC calls). This is done on platforms which
> don't have TrustZone (which programs the modem SIDs) to prevent the
> following global faults seen on Cheza/Trogdor:
>
> Cheza:
> arm-smmu 15000000.iommu: Unexpected global fault, this could be serious
> arm-smmu 15000000.iommu: GFSR 0x80000002, GFSYNR0 0x00000000,
> GFSYNR1 0x00000781, GFSYNR2 0x00000000
>
> Trogdor:
> arm-smmu 15000000.iommu: Unexpected global fault, this could be serious
> arm-smmu 15000000.iommu: GFSR 0x80000002, GFSYNR0 0x00000000,
> GFSYNR1 0x00000461, GFSYNR2 0x00000000
>
> V2:
> * Request direct mapping from SoC-specific corner of the SMMU
> driver [Robin]
> * Add iommu property to remoteproc modem node on Cheza
>
> Depends on:
> https://lore.kernel.org/patchwork/cover/1183528/
>
> Sibi Sankar (3):
> dt-bindings: remoteproc: qcom: Add iommus property
> remoteproc: qcom_q6v5_mss: Request direct mapping for modem device
iommu: arm-smmu-qcom: Request direct mapping for modem device
sry should have been ^^ instead
> arm64: dts: qcom: sdm845-cheza: Add iommus property
>
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 3 +++
> arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 4 ++++
> drivers/iommu/arm-smmu-qcom.c | 6 ++++++
> 3 files changed, 13 insertions(+)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-03-17 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 15:09 [PATCH v2 0/3] Request direct mapping for modem device Sibi Sankar
2020-03-17 15:09 ` Sibi Sankar
2020-03-17 15:09 ` [PATCH v2 1/3] dt-bindings: remoteproc: qcom: Add iommus property Sibi Sankar
2020-03-17 15:09 ` Sibi Sankar
2020-03-30 22:11 ` Rob Herring
2020-03-30 22:11 ` Rob Herring
2020-03-30 22:11 ` Rob Herring
2020-03-17 15:09 ` [PATCH v2 2/3] remoteproc: qcom_q6v5_mss: Request direct mapping for modem device Sibi Sankar
2020-03-17 15:09 ` Sibi Sankar
2020-03-17 15:09 ` [PATCH v2 3/3] arm64: dts: qcom: sdm845-cheza: Add iommus property Sibi Sankar
2020-03-17 15:09 ` Sibi Sankar
2020-03-17 15:52 ` Sibi Sankar [this message]
2020-03-17 15:52 ` [PATCH v2 0/3] Request direct mapping for modem device Sibi Sankar
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=fe9bb128563bea9798573ac9eec1d214@codeaurora.org \
--to=sibis@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=saiprakash.ranjan@codeaurora.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 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.