From: Philipp Zabel <p.zabel@pengutronix.de>
To: "Enrico Weigelt, metux IT consult" <weigelt@melag.de>
Cc: Jean-Michel Hautbois <jean-michel.hautbois@veo-labs.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Kamil Debski <k.debski@samsung.com>,
Ian Molton <imolton@ad-holdings.co.uk>,
Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>,
Sascha Hauer <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH v2 2/5] gpu: ipu-v3: Add mem2mem image conversion support to IC
Date: Thu, 28 May 2015 13:59:46 +0200 [thread overview]
Message-ID: <1432814386.3228.51.camel@pengutronix.de> (raw)
In-Reply-To: <5566FC95.3020000@melag.de>
Am Donnerstag, den 28.05.2015, 13:31 +0200 schrieb Enrico Weigelt, metux
IT consult:
> Am 28.05.2015 um 12:44 schrieb Philipp Zabel:
>
> Hi,
>
> >> 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@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
mmio.
[...]
> 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.
regards
Philipp
next prev parent reply other threads:[~2015-05-28 11:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 10:22 [PATCH v2 0/5] i.MX5/6 mem2mem scaler Philipp Zabel
2015-03-18 10:22 ` [PATCH v2 1/5] gpu: ipu-v3: Add missing IDMAC channel names Philipp Zabel
2015-03-18 10:22 ` [PATCH v2 2/5] gpu: ipu-v3: Add mem2mem image conversion support to IC Philipp Zabel
2015-05-27 18:42 ` Jean-Michel Hautbois
2015-05-28 9:00 ` Enrico Weigelt, metux IT consult
2015-05-28 10:44 ` Philipp Zabel
2015-05-28 11:31 ` Enrico Weigelt, metux IT consult
2015-05-28 11:59 ` Philipp Zabel [this message]
2015-05-28 17:38 ` Enrico Weigelt, metux IT consult
2015-05-28 17:54 ` Robert Schwebel
2015-05-29 9:02 ` Enrico Weigelt, metux IT consult
2015-05-28 10:35 ` Philipp Zabel
2015-03-18 10:22 ` [PATCH v2 3/5] gpu: ipu-v3: Register scaler platform device Philipp Zabel
2015-03-18 10:22 ` [PATCH v2 4/5] [media] imx-ipu: Add ipu media common code Philipp Zabel
2015-03-18 10:22 ` [PATCH v2 5/5] [media] imx-ipu: Add i.MX IPUv3 scaler driver Philipp Zabel
2015-04-10 13:03 ` [PATCH v2 0/5] i.MX5/6 mem2mem scaler Jean-Michel Hautbois
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1432814386.3228.51.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hans.verkuil@cisco.com \
--cc=imolton@ad-holdings.co.uk \
--cc=jean-michel.hautbois@veo-labs.com \
--cc=jean-michel.hautbois@vodalys.com \
--cc=k.debski@samsung.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=s.hauer@pengutronix.de \
--cc=slongerbeam@gmail.com \
--cc=weigelt@melag.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).