[PATCH v2 2/5] gpu: ipu-v3: Add mem2mem image conversion support to IC
p.zabel at pengutronix.de
Thu May 28 04:59:46 PDT 2015
Am Donnerstag, den 28.05.2015, 13:31 +0200 schrieb Enrico Weigelt, metux
> Am 28.05.2015 um 12:44 schrieb Philipp Zabel:
> >> Are these patches same as in your git branch tmp/imx-ipu-scaler ?
> > No, that is an older version.
> Where can I get the recent ones ?
> Could you push it to your public repo ?
I've updated the tmp/imx-ipu-scaler branch.
> >> when using it w/ gst for video playback, can be directly pass buffers
> >> between VPU, IPU and FB (or let them directly write into shared
> >> buffers), so CPU doesn't need to act on each frame for each step
> >> in the decoding pipeline ?
> > Check out the (capture/output-)io-mode parameters, that's what the
> > dmabuf/dmabuf-import option pairs are for.
> Tried dmabuf, but load stays at the same (77..80% CPU, 1.2 loadavg).
> dmabuf-import doesnt run at all:
> root at KoMo:/usr/share/videos/komo gst-launch-1.0 filesrc
> location=montage.mp4 \! qtdemux \! h264parse \! v4l2video4dec
> output-io-mode=5 \! v4l2video0convert capture-io-mode=5 output-io-mode=4
> \! fbdevsink
That should be capture-io-mode=dmabuf for the decoder and
output-io-mode=dmabuf-import for the converter element. h264parse
doesn't provide and fbdevsink can't handle dmabufs, so the decoder's
output-io-mode and the converter's capture-io-mode should be kept as
> By the way: do you have any idea whether the proprietary driver
> (or the gpus itself) might talk to ipu and vpu ?
Not that I am aware of.
More information about the dri-devel