From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>
Cc: "Steve Longerbeam" <slongerbeam@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Frédéric Sureau" <frederic.sureau@vodalys.com>,
"Fabio Estevam" <fabio.estevam@freescale.com>
Subject: Re: i.MX6 CSC and scaler
Date: Tue, 16 Dec 2014 09:15:36 -0500 [thread overview]
Message-ID: <54903E88.2070701@collabora.com> (raw)
In-Reply-To: <1418736635.3374.64.camel@pengutronix.de>
Le 2014-12-16 08:30, Philipp Zabel a écrit :
> For the IPU IC mem2mem scaler/CSC, v4l2transform with scaling capability
> would be the perfect fit
Thanks you for clarifying. Jean-Michel, are you going to work on this ?
If so, feel free to contact me directly for pointers. You'll find me as
stormer on IRC freenode on both #v4l2 and #gstreamer.
What would need to be done:
a) Import scaler negotiation code from videoscale element, and merge it
into v4l2transform negotiation. It is likely that wtay (Wim Tayman) have
some code already for you, has on the SW side he is currently working on
merging videoscale and videoconvert together as it's faster this way.
b) Complete the handling of G_CROP (if required add G_SELECTION). Most
HW scaler will allocate aligned buffers, but can reach a 1 or 2 pixels
precision through CROP or SELECTION.
cheers,
Nicolas
next prev parent reply other threads:[~2014-12-16 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 17:03 i.MX6 CSC and scaler Jean-Michel Hautbois
2014-12-15 18:23 ` Steve Longerbeam
2014-12-15 18:52 ` Nicolas Dufresne
2014-12-15 21:27 ` Jean-Michel Hautbois
2014-12-16 13:30 ` Philipp Zabel
2014-12-16 14:15 ` Nicolas Dufresne [this message]
2014-12-16 14:27 ` Jean-Michel Hautbois
2014-12-16 14:50 ` Nicolas Dufresne
2014-12-17 13:12 ` Jean-Michel Hautbois
2014-12-17 13:45 ` Nicolas Dufresne
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=54903E88.2070701@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=fabio.estevam@freescale.com \
--cc=frederic.sureau@vodalys.com \
--cc=jean-michel.hautbois@vodalys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=slongerbeam@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.