Am Montag, 15. Januar 2018, 18:15:37 CET schrieb Thierry Escande: > From: ?rjan Eide <orjan.eide at arm.com> > > When mapping external DMA-bufs through the PRIME mmap call, we might be > given an offset which has to be respected. However for the internal DRM > GEM mmap path, we have to ignore the fake mmap offset used to identify > the buffer only. Currently the code always zeroes out vma->vm_pgoff, > which breaks the former. > > This patch fixes the problem by moving the vm_pgoff assignment to a > function that is used only for GEM mmap path, so that the PRIME path > retains the original offset. > > Cc: Daniel Kurtz <djkurtz at chromium.org> > Signed-off-by: ?rjan Eide <orjan.eide at arm.com> > Signed-off-by: Tomasz Figa <tfiga at chromium.org> > Signed-off-by: Sean Paul <seanpaul at chromium.org> > Signed-off-by: Thierry Escande <thierry.escande at collabora.com> On rk3036 + lima and rk3328 + lima Tested-by: Heiko Stuebner <heiko at sntech.de>
