iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Will Deacon <will@kernel.org>
Cc: Patrick Daly <pdaly@codeaurora.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	iommu@lists.linux-foundation.org,
	Thierry Reding <treding@nvidia.com>,
	Robin Murphy <robin.murphy@arm.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Pratik Patel <pratikp@codeaurora.org>
Subject: Re: [PATCH 0/3] iommu/arm-smmu: Qualcomm bootsplash/efifb
Date: Mon, 24 May 2021 13:03:39 +0100	[thread overview]
Message-ID: <CAF2Aj3iKk2LSA5XC76pNiLV8a76BkibUitof-dix8rqkc0qiow@mail.gmail.com> (raw)
In-Reply-To: <20200108091641.GA15147@willie-the-truck>


[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]

On Wed, 8 Jan 2020 at 09:16, Will Deacon <will@kernel.org> wrote:

> On Thu, Dec 26, 2019 at 02:17:06PM -0800, Bjorn Andersson wrote:
> > These patches implements the stream mapping inheritance that's necessary
> in
> > order to not hit a security violation as the display hardware looses its
> stream
> > mapping during initialization of arm-smmu in various Qualcomm platforms.
> >
> > This was previously posted as an RFC [1], changes since then involves the
> > rebase and migration of the read-back code to the Qualcomm specific
> > implementation, the mapping is maintained indefinitely - to handle probe
> > deferring clients - and rewritten commit messages.
>
> I don't think we should solve this in a Qualcomm-specific manner. Please
> can
> you take a look at the proposal from Thierry [1] and see whether or not it
> works for you?
>

Did this or Thierry's solution ever gain traction?

Or are all the parties still 'solving' this downstream?


> Thanks,
>
> Will
>
> [1]
> https://lore.kernel.org/lkml/20191209150748.2471814-1-thierry.reding@gmail.com
>


-- 
Lee Jones [李琼斯]
Linaro Services Senior Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

[-- Attachment #1.2: Type: text/html, Size: 2218 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2021-05-24 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-26 22:17 [PATCH 0/3] iommu/arm-smmu: Qualcomm bootsplash/efifb Bjorn Andersson
2019-12-26 22:17 ` [PATCH 1/3] iommu/arm-smmu: Don't blindly use first SMR to calculate mask Bjorn Andersson
2019-12-26 22:17 ` [PATCH 2/3] iommu/arm-smmu: Expose s2cr and smr structs to impl Bjorn Andersson
2019-12-26 22:17 ` [PATCH 3/3] iommu/arm-smmu: Allow inherting stream mapping from bootloader Bjorn Andersson
2020-01-08  9:16 ` [PATCH 0/3] iommu/arm-smmu: Qualcomm bootsplash/efifb Will Deacon
2021-05-24 12:03   ` Lee Jones [this message]
2021-05-24 12:48     ` Robin Murphy
2021-05-25  3:28     ` Bjorn Andersson

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=CAF2Aj3iKk2LSA5XC76pNiLV8a76BkibUitof-dix8rqkc0qiow@mail.gmail.com \
    --to=lee.jones@linaro.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pdaly@codeaurora.org \
    --cc=pratikp@codeaurora.org \
    --cc=robin.murphy@arm.com \
    --cc=treding@nvidia.com \
    --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).