mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-11-01 22:58:50 -04:00
buffer: add MAPPABLE data flag
Add a MAPPABLE data flag that hints that the fd in the data is mappable with a simple mmap/munmap. Normally, DmaBuf is not mappable like that unless explicitly indicated with this flag. Set the MAPPABLE flag on the DmaBuf from v4l2 and libcamera fd. When asked, mmap the buffer memory in all cases when the MAPPABLE flag is set. This solves the case where v4l2 has exported DmaBuf and is streaming to node A and then node B links but doesn't get automatically mmaped memory. Fixes #3840
This commit is contained in:
parent
4715fa1775
commit
858d4e9e1c
6 changed files with 11 additions and 4 deletions
|
|
@ -805,6 +805,7 @@ mmap_init(struct impl *impl, struct port *port,
|
|||
|
||||
if (port->memtype == SPA_DATA_DmaBuf ||
|
||||
port->memtype == SPA_DATA_MemFd) {
|
||||
d[j].flags |= SPA_DATA_FLAG_MAPPABLE;
|
||||
d[j].fd = bufs[i]->planes()[j].fd.get();
|
||||
spa_log_debug(impl->log, "Got fd = %ld for buffer: #%d", d[j].fd, i);
|
||||
d[j].data = NULL;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue