From: Will Deacon <will@kernel.org>
To: Thierry Reding <treding@nvidia.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Joerg Roedel <joro@8bytes.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Clark <robdclark@chromium.org>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] iommu/arm-smmu-qcom: Support maintaining bootloader mappings
Date: Thu, 29 Oct 2020 18:34:18 +0000 [thread overview]
Message-ID: <160399513141.1314250.8831514745970142969.b4-ty@kernel.org> (raw)
In-Reply-To: <20201019182323.3162386-1-bjorn.andersson@linaro.org>
On Mon, 19 Oct 2020 11:23:20 -0700, 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.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/3] iommu/arm-smmu: Allow implementation specific write_s2cr
https://git.kernel.org/will/c/56b75b51ed6d
[2/3] iommu/arm-smmu-qcom: Read back stream mappings
https://git.kernel.org/will/c/07a7f2caaa5a
[3/3] iommu/arm-smmu-qcom: Implement S2CR quirk
https://git.kernel.org/will/c/f9081b8ff593
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: Thierry Reding <treding@nvidia.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Joerg Roedel <joro@8bytes.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Clark <robdclark@chromium.org>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: Will Deacon <will@kernel.org>,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-arm-msm@vger.kernel.org,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/3] iommu/arm-smmu-qcom: Support maintaining bootloader mappings
Date: Thu, 29 Oct 2020 18:34:18 +0000 [thread overview]
Message-ID: <160399513141.1314250.8831514745970142969.b4-ty@kernel.org> (raw)
In-Reply-To: <20201019182323.3162386-1-bjorn.andersson@linaro.org>
On Mon, 19 Oct 2020 11:23:20 -0700, 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.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/3] iommu/arm-smmu: Allow implementation specific write_s2cr
https://git.kernel.org/will/c/56b75b51ed6d
[2/3] iommu/arm-smmu-qcom: Read back stream mappings
https://git.kernel.org/will/c/07a7f2caaa5a
[3/3] iommu/arm-smmu-qcom: Implement S2CR quirk
https://git.kernel.org/will/c/f9081b8ff593
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: Thierry Reding <treding@nvidia.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Joerg Roedel <joro@8bytes.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Clark <robdclark@chromium.org>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: Will Deacon <will@kernel.org>,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-arm-msm@vger.kernel.org,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/3] iommu/arm-smmu-qcom: Support maintaining bootloader mappings
Date: Thu, 29 Oct 2020 18:34:18 +0000 [thread overview]
Message-ID: <160399513141.1314250.8831514745970142969.b4-ty@kernel.org> (raw)
In-Reply-To: <20201019182323.3162386-1-bjorn.andersson@linaro.org>
On Mon, 19 Oct 2020 11:23:20 -0700, 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.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/3] iommu/arm-smmu: Allow implementation specific write_s2cr
https://git.kernel.org/will/c/56b75b51ed6d
[2/3] iommu/arm-smmu-qcom: Read back stream mappings
https://git.kernel.org/will/c/07a7f2caaa5a
[3/3] iommu/arm-smmu-qcom: Implement S2CR quirk
https://git.kernel.org/will/c/f9081b8ff593
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-10-29 18:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 18:23 [PATCH v5 0/3] iommu/arm-smmu-qcom: Support maintaining bootloader mappings Bjorn Andersson
2020-10-19 18:23 ` Bjorn Andersson
2020-10-19 18:23 ` Bjorn Andersson
2020-10-19 18:23 ` [PATCH v5 1/3] iommu/arm-smmu: Allow implementation specific write_s2cr Bjorn Andersson
2020-10-19 18:23 ` Bjorn Andersson
2020-10-19 18:23 ` Bjorn Andersson
2020-10-19 18:23 ` [PATCH v5 2/3] iommu/arm-smmu-qcom: Read back stream mappings Bjorn Andersson
2020-10-19 18:23 ` Bjorn Andersson
2020-10-19 18:23 ` Bjorn Andersson
2020-10-19 18:50 ` Robin Murphy
2020-10-19 18:50 ` Robin Murphy
2020-10-19 18:50 ` Robin Murphy
2020-10-19 18:23 ` [PATCH v5 3/3] iommu/arm-smmu-qcom: Implement S2CR quirk Bjorn Andersson
2020-10-19 18:23 ` Bjorn Andersson
2020-10-19 18:23 ` Bjorn Andersson
2020-10-19 19:02 ` Robin Murphy
2020-10-19 19:02 ` Robin Murphy
2020-10-19 19:02 ` Robin Murphy
2020-10-22 17:14 ` [PATCH v5 0/3] iommu/arm-smmu-qcom: Support maintaining bootloader mappings Steev Klimaszewski
2020-10-22 17:14 ` Steev Klimaszewski
2020-10-22 17:14 ` Steev Klimaszewski
2020-10-29 18:34 ` Will Deacon [this message]
2020-10-29 18:34 ` Will Deacon
2020-10-29 18:34 ` Will Deacon
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm
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=160399513141.1314250.8831514745970142969.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jcrouse@codeaurora.org \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=robin.murphy@arm.com \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=treding@nvidia.com \
/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.