From: Stephen Boyd <swboyd@chromium.org>
To: Sibi Sankar <sibis@codeaurora.org>,
joro@8bytes.org, robin.murphy@arm.com, will@kernel.org
Cc: linux-arm-msm@vger.kernel.org, dianders@chromium.org,
evgreen@chromium.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, mka@chromium.org,
Sibi Sankar <sibis@codeaurora.org>,
bjorn.andersson@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6] iommu/arm-smmu-qcom: Request direct mapping for modem device
Date: Mon, 11 May 2020 12:37:09 -0700 [thread overview]
Message-ID: <158922582972.26370.14084228362776489859@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200511175532.25874-1-sibis@codeaurora.org>
Quoting Sibi Sankar (2020-05-11 10:55:32)
> The modem remote processor has two access paths to DDR. One path is
> directly connected to DDR and another path goes through an SMMU. The
> SMMU path is configured to be a direct mapping because it's used by
> various peripherals in the modem subsystem. Typically this direct
> mapping is configured statically at EL2 by QHEE (Qualcomm's Hypervisor
> Execution Environment) before the kernel is entered.
>
> In certain firmware configuration, especially when the kernel is already
> in full control of the SMMU, defer programming the modem SIDs to the
> kernel. Let's add compatibles here so that we can have the kernel
> program the SIDs for the modem in these cases.
>
> Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
> ---
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-05-11 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 17:55 [PATCH v6] iommu/arm-smmu-qcom: Request direct mapping for modem device Sibi Sankar
2020-05-11 19:31 ` Bjorn Andersson
2020-05-11 19:37 ` Stephen Boyd [this message]
2020-05-15 8:18 ` Sibi Sankar
2020-05-18 23: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=158922582972.26370.14084228362776489859@swboyd.mtv.corp.google.com \
--to=swboyd@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robin.murphy@arm.com \
--cc=sibis@codeaurora.org \
--cc=will@kernel.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).