[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190507063618.GA28147@lst.de>
Date: Tue, 7 May 2019 08:36:18 +0200
From: Christoph Hellwig <hch@....de>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Cc: Christoph Hellwig <hch@....de>, Ralf Baechle <ralf@...ux-mips.org>,
Paul Burton <paul.burton@...s.com>,
James Hogan <jhogan@...nel.org>,
Ley Foon Tan <lftan@...era.com>,
Michal Simek <monstr@...str.eu>, linux-mips@...r.kernel.org,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
linux-fbdev@...r.kernel.org
Subject: Re: [PATCH 2/7] au1100fb: fix DMA API abuse
On Mon, May 06, 2019 at 03:49:35PM +0200, Bartlomiej Zolnierkiewicz wrote:
>
> On 04/30/2019 01:00 PM, Christoph Hellwig wrote:
> > Virtual addresses return from dma(m)_alloc_coherent are opaque in what
> > backs then, and drivers must not poke into them. Switch the driver
> > to use the generic DMA API mmap helper to avoid these games.
> >
> > Signed-off-by: Christoph Hellwig <hch@....de>
>
> Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Given this actually fixes issues with the current driver, what do you
think of taking it for 5.2 through your tree? Also au1200fb has
basically the same issues, just without abusing the CAC_ADDR helper,
I could send you a patch for that one as well.
Powered by blists - more mailing lists