linux-kernel - Re: [PATCH v6] iommu/arm-smmu-qcom: Request direct mapping for modem device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <158981250642.239015.17275693427372248725.b4-ty@kernel.org>
Date:   Tue, 19 May 2020 00:04:08 +0100
From:   Will Deacon <will@...nel.org>
To:     robin.murphy@....com, swboyd@...omium.org, joro@...tes.org,
        Sibi Sankar <sibis@...eaurora.org>
Cc:     catalin.marinas@....com, Will Deacon <will@...nel.org>,
        dianders@...omium.org, iommu@...ts.linux-foundation.org,
        bjorn.andersson@...aro.org, mka@...omium.org,
        linux-arm-msm@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, evgreen@...omium.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6] iommu/arm-smmu-qcom: Request direct mapping for modem device

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