From: Sven Van Asbroeck <thesven73@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-media@vger.kernel.org,
Hans Verkuil <hans.verkuil@cisco.com>,
Tim Harvey <tharvey@gateworks.com>
Subject: Re: [v8] media: imx: add mem2mem device
Date: Wed, 29 May 2019 11:44:31 -0400 [thread overview]
Message-ID: <20190529154431.11177-1-TheSven73@gmail.com> (raw)
In-Reply-To: <20190418164414.29373-1-p.zabel@pengutronix.de>
Thank you all (and especially Philipp) for this amazing work !
One of the main uses for the VPU scaler is to convert from video file
resolution to display resolution. E.g. the source video is 1080p, but the
display videomode is only 720p.
Unfortunately when I connect CODA/h264 decode to the VPU scaler, performance
drops to about half. But on the non-mainline Freescale kernel, even with
the rescale, I still get 30fps.
Mainline kernel + v8 imx rescaler patch:
A) 1080p30 source video -> CODA h264 decode -> drm 1080p: near full speed (28fps)
B) 1080p30 source video -> CODA h264 decode -> VPU scaler 1080p->720p ->
drm 720p: only half speed (15fps)
Freescale non-mainline kernel:
C) 1080p30 source video -> CODA h264 decode -> VPU scaler 1080p->720p ->
v4l2out 720p: full speed (30fps)
Question:
- is this expected behaviour ? A regression wrt. the Freescale kernel?
- perhaps I am missing something in the gstreamer pipeline ?
Gstreamer pipelines:
--------------------
A) gst-launch-1.0 filesrc location=/home/default/jellyfish-10-mbps-hd-h264.mkv !
matroskademux ! h264parse ! v4l2h264dec ! kmssink can-scale=0
B) gst-launch-1.0 filesrc location=/home/default/jellyfish-10-mbps-hd-h264.mkv !
matroskademux ! h264parse ! v4l2h264dec ! v4l2video8convert ! video/x-raw,width=
1280,height=720 ! kmssink can-scale=0
C) gst-launch-0.10 filesrc location=/home/default/jellyfish-10-mbps-hd-h264.
mkv ! decodebin ! mfw_v4lsink
I have tried various values for capture-io-mode/output-io-mode.
imx6q
v8 imx scaler patch backported to 4.19 mainline kernel.
GStreamer 1.14.4
next prev parent reply other threads:[~2019-05-29 15:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 16:44 [PATCH v8] media: imx: add mem2mem device Philipp Zabel
2019-05-10 13:03 ` Hans Verkuil
2019-05-29 15:44 ` Sven Van Asbroeck [this message]
2019-05-29 16:53 ` [v8] " Fabio Estevam
2019-05-29 17:20 ` Sven Van Asbroeck
2019-05-29 20:55 ` Sven Van Asbroeck
2019-05-29 22:19 ` Fabio Estevam
2019-05-29 23:48 ` Nicolas Dufresne
2019-05-29 23:52 ` Nicolas Dufresne
2019-05-31 15:34 ` Nicolas Dufresne
2019-05-31 16:07 ` Sven Van Asbroeck
2019-05-31 17:34 ` Nicolas Dufresne
2019-05-30 21:09 ` Nicolas Dufresne
2019-05-30 21:34 ` Sven Van Asbroeck
2019-05-30 22:18 ` Fabio Estevam
2019-05-31 0:26 ` Sven Van Asbroeck
2019-05-31 0:26 ` Robin Gong
2019-05-31 21:58 ` Sven Van Asbroeck
2019-06-04 8:51 ` Robin Gong
2019-06-04 17:57 ` Sven Van Asbroeck
2019-06-05 10:08 ` Robin Gong
2019-06-05 13:51 ` Sven Van Asbroeck
2019-06-06 2:32 ` Robin Gong
2019-06-06 13:34 ` Sven Van Asbroeck
2019-06-10 9:09 ` Robin Gong
2019-06-10 15:46 ` Sven Van Asbroeck
2019-06-11 9:09 ` Robin Gong
2019-06-11 9:17 ` Robin Gong
2019-06-11 17:30 ` Sven Van Asbroeck
2019-06-13 8:52 ` Robin Gong
2019-06-13 14:00 ` Sven Van Asbroeck
2019-05-31 21:16 ` Sven Van Asbroeck
2019-06-12 1:08 ` [PATCH v8] " Steve Longerbeam
2019-06-14 14:13 ` Philipp Zabel
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=20190529154431.11177-1-TheSven73@gmail.com \
--to=thesven73@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=tharvey@gateworks.com \
/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