[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc462189-d5de-bb8d-31b5-6fb87a6edbdb@kali.org>
Date: Thu, 22 Oct 2020 12:14:38 -0500
From: Steev Klimaszewski <steev@...i.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>,
Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Joerg Roedel <joro@...tes.org>,
Sai Prakash Ranjan <saiprakash.ranjan@...eaurora.org>,
Jordan Crouse <jcrouse@...eaurora.org>,
Thierry Reding <treding@...dia.com>,
Rob Clark <robdclark@...omium.org>
Cc: linux-arm-kernel@...ts.infradead.org,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v5 0/3] iommu/arm-smmu-qcom: Support maintaining
bootloader mappings
On 10/19/20 1:23 PM, Bjorn Andersson wrote:
> This is the revised fourth attempt of inheriting the stream mapping for
> the framebuffer on many Qualcomm platforms, in order to not hit
> catastrophic faults during arm-smmu initialization.
>
> The new approach does, based on Robin's suggestion, take a much more
> direct approach with the allocation of a context bank for bypass
> emulation and use of this context bank pretty much isolated to the
> Qualcomm specific implementation.
>
> The patchset has been tested to boot DB845c and RB5 (with splash screen)
> and Lenovo Yoga C630 (with EFI framebuffer).
>
> Bjorn Andersson (3):
> iommu/arm-smmu: Allow implementation specific write_s2cr
> iommu/arm-smmu-qcom: Read back stream mappings
> iommu/arm-smmu-qcom: Implement S2CR quirk
>
> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 90 ++++++++++++++++++++++
> drivers/iommu/arm/arm-smmu/arm-smmu.c | 13 +++-
> drivers/iommu/arm/arm-smmu/arm-smmu.h | 1 +
> 3 files changed, 101 insertions(+), 3 deletions(-)
>
Tested series here on my Lenovo C630.
Tested-by: Steev Klimaszewski <steev@...i.org>
Powered by blists - more mailing lists