On (21/07/07 23:10), Tomasz Figa wrote: > > > > > > > > I guess this should address the case when > > > > > > > > "after allocating the buffer, the buffer is exported as a dma_buf and > > > > another device calls dma_buf_ops vb2_dc_dmabuf_ops_vmap, which in turn > > > > calls dma_buf_map_set_vaddr(map, buf->vaddr); with a NULL buf->vaddr" > > > > > > Sorry, I fail to get what this is about. Where does this quote come from? > > > > Bottom half of https://lore.kernel.org/lkml/10a0903a-e295-5cba-683a-1eb89a0804ed@xxxxxxxxx/ > > I see, thanks for the pointer. Yes, vb2_dc_dmabuf_ops_vmap() needs to > be changed so that it calls vb2_dc_vaddr() internally instead of > relying on buf->vaddr directly. Done.
