From: Rob Clark <robdclark@gmail.com>
To: Tomasz Figa <tfiga@chromium.org>
Cc: freedreno <freedreno@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, David Airlie <airlied@linux.ie>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Will Deacon <will.deacon@arm.com>,
Doug Anderson <dianders@chromium.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux IOMMU <iommu@lists.linux-foundation.org>,
Rob Herring <robh+dt@kernel.org>,
Sean Paul <seanpaul@chromium.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [Freedreno] [PATCH] of/device: add blacklist for iommu dma_ops
Date: Wed, 5 Jun 2019 05:57:16 -0700 [thread overview]
Message-ID: <CAF6AEGuj=QmEWZVzHMtoDgO0M0t-W9+tay5F4AKYThZqy=nkdA@mail.gmail.com> (raw)
In-Reply-To: <CAAFQd5Dmr+xyd4dyc_44vJFpNpwK6+MgG+ensoey59HgbxXV6g@mail.gmail.com>
On Tue, Jun 4, 2019 at 11:58 PM Tomasz Figa <tfiga@chromium.org> wrote:
>
> But first of all, I remember Marek already submitted some patches long
> ago that extended struct driver with some flag that means that the
> driver doesn't want the IOMMU to be attached before probe. Why
> wouldn't that work? Sounds like a perfect opt-out solution.
Actually, yeah.. we should do that. That is the simplest solution.
BR,
-R
next prev parent reply other threads:[~2019-06-05 12:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 16:53 [PATCH] of/device: add blacklist for iommu dma_ops Rob Clark
2018-12-03 0:10 ` Tomasz Figa
[not found] ` <CAAFQd5CWRKGA2=TEpYvnLuBzu6=2h1i_YtmN_FusyFuLy5BpdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-03 11:06 ` Marek Szyprowski
2018-12-03 12:45 ` Robin Murphy
[not found] ` <a29008a3-8eff-260d-5c93-9757a729f9e0-5wv7dgnIgG8@public.gmane.org>
2018-12-03 14:16 ` Rob Clark
2018-12-03 14:26 ` Rob Clark
[not found] ` <CAF6AEGvo0-oWNKcz6BEA8Eh250FL4rXaBVYXuJGBtshPk4jz+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-04 6:34 ` Vivek Gautam
[not found] ` <20181201165348.24140-1-robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-12-04 22:29 ` Rob Herring
2019-05-10 14:35 ` Rob Clark
2019-06-02 19:08 ` Rob Clark
2019-06-03 6:20 ` Tomasz Figa
2019-06-03 7:56 ` Vivek Gautam
2019-06-03 10:44 ` Rob Clark
2019-06-03 11:12 ` Vivek Gautam
2019-06-03 11:17 ` Christoph Hellwig
2019-06-03 11:32 ` Vivek Gautam
2019-06-03 10:47 ` Rob Clark
2019-06-03 11:14 ` Robin Murphy
2019-06-03 13:20 ` Rob Clark
2019-06-03 13:54 ` Thierry Reding
2019-06-03 14:20 ` Rob Clark
2019-06-03 14:40 ` Thierry Reding
2019-06-03 14:48 ` Jordan Crouse
2019-06-03 13:39 ` Thierry Reding
2019-06-05 6:57 ` Tomasz Figa
2019-06-05 12:57 ` Rob Clark [this message]
2019-06-05 13:18 ` [Freedreno] " Marek Szyprowski
2019-06-05 14:16 ` Rob Clark
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='CAF6AEGuj=QmEWZVzHMtoDgO0M0t-W9+tay5F4AKYThZqy=nkdA@mail.gmail.com' \
--to=robdclark@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=seanpaul@chromium.org \
--cc=tfiga@chromium.org \
--cc=vivek.gautam@codeaurora.org \
--cc=will.deacon@arm.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 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).