From: Will Deacon <will@kernel.org>
To: robin.murphy@arm.com, swboyd@chromium.org, joro@8bytes.org,
Sibi Sankar <sibis@codeaurora.org>
Cc: catalin.marinas@arm.com, Will Deacon <will@kernel.org>,
dianders@chromium.org, iommu@lists.linux-foundation.org,
bjorn.andersson@linaro.org, mka@chromium.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, evgreen@chromium.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] iommu/arm-smmu-qcom: Request direct mapping for modem device
Date: Tue, 19 May 2020 00:04:08 +0100 [thread overview]
Message-ID: <158981250642.239015.17275693427372248725.b4-ty@kernel.org> (raw)
In-Reply-To: <20200511175532.25874-1-sibis@codeaurora.org>
On Mon, 11 May 2020 23:25:32 +0530, Sibi Sankar wrote:
> 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.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/1] iommu/arm-smmu-qcom: Request direct mapping for modem device
https://git.kernel.org/will/c/d100ff3843b7
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: robin.murphy@arm.com, swboyd@chromium.org, joro@8bytes.org,
Sibi Sankar <sibis@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
dianders@chromium.org, evgreen@chromium.org,
bjorn.andersson@linaro.org, iommu@lists.linux-foundation.org,
mka@chromium.org, linux-arm-msm@vger.kernel.org,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6] iommu/arm-smmu-qcom: Request direct mapping for modem device
Date: Tue, 19 May 2020 00:04:08 +0100 [thread overview]
Message-ID: <158981250642.239015.17275693427372248725.b4-ty@kernel.org> (raw)
In-Reply-To: <20200511175532.25874-1-sibis@codeaurora.org>
On Mon, 11 May 2020 23:25:32 +0530, Sibi Sankar wrote:
> 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.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/1] iommu/arm-smmu-qcom: Request direct mapping for modem device
https://git.kernel.org/will/c/d100ff3843b7
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: robin.murphy@arm.com, swboyd@chromium.org, joro@8bytes.org,
Sibi Sankar <sibis@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
dianders@chromium.org, evgreen@chromium.org,
bjorn.andersson@linaro.org, iommu@lists.linux-foundation.org,
mka@chromium.org, linux-arm-msm@vger.kernel.org,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6] iommu/arm-smmu-qcom: Request direct mapping for modem device
Date: Tue, 19 May 2020 00:04:08 +0100 [thread overview]
Message-ID: <158981250642.239015.17275693427372248725.b4-ty@kernel.org> (raw)
In-Reply-To: <20200511175532.25874-1-sibis@codeaurora.org>
On Mon, 11 May 2020 23:25:32 +0530, Sibi Sankar wrote:
> 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.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/1] iommu/arm-smmu-qcom: Request direct mapping for modem device
https://git.kernel.org/will/c/d100ff3843b7
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-18 23:04 UTC|newest]
Thread overview: 15+ 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 17:55 ` Sibi Sankar
2020-05-11 17:55 ` Sibi Sankar
2020-05-11 19:31 ` Bjorn Andersson
2020-05-11 19:31 ` Bjorn Andersson
2020-05-11 19:31 ` Bjorn Andersson
2020-05-11 19:37 ` Stephen Boyd
2020-05-11 19:37 ` Stephen Boyd
2020-05-11 19:37 ` Stephen Boyd
2020-05-15 8:18 ` Sibi Sankar
2020-05-15 8:18 ` Sibi Sankar
2020-05-15 8:18 ` Sibi Sankar
2020-05-18 23:04 ` Will Deacon [this message]
2020-05-18 23:04 ` Will Deacon
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=158981250642.239015.17275693427372248725.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--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=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 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.