Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

Follow-up from "v4l2bufferpool: request the maximum number of buffers for DMABUF"

The following discussion from !560 (merged) should be addressed:

@ndufresne started a discussion:
This patch introduce a regression (stall). Removing the backport tag, and will revert unless a proper fix is provided.

Pipeline to reproduce:
```
gst-launch-1.0 v4l2src num-buffers=10 io-mode=dmabuf-import ! v4l2fwhtenc ! fakesink
```
What happens with this patch is that v4l2src will try and queue 32 buffers, which will try and allocated 32 buffers from the other pool, but the otherpool was configured with 4 buffers and cannot grow (no allocation support).