[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF6AEGuj=QmEWZVzHMtoDgO0M0t-W9+tay5F4AKYThZqy=nkdA@mail.gmail.com>
Date: Wed, 5 Jun 2019 05:57:16 -0700
From: Rob Clark <robdclark@...il.com>
To: Tomasz Figa <tfiga@...omium.org>
Cc: freedreno <freedreno@...ts.freedesktop.org>,
Daniel Vetter <daniel@...ll.ch>,
Frank Rowand <frowand.list@...il.com>,
devicetree@...r.kernel.org, David Airlie <airlied@...ux.ie>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Will Deacon <will.deacon@....com>,
Doug Anderson <dianders@...omium.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux IOMMU <iommu@...ts.linux-foundation.org>,
Rob Herring <robh+dt@...nel.org>,
Sean Paul <seanpaul@...omium.org>,
Vivek Gautam <vivek.gautam@...eaurora.org>,
Robin Murphy <robin.murphy@....com>,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [Freedreno] [PATCH] of/device: add blacklist for iommu dma_ops
On Tue, Jun 4, 2019 at 11:58 PM Tomasz Figa <tfiga@...omium.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
Powered by blists - more mailing lists