From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Support for H.264/MPEG4 encoder (VPU) in i.MX27.
Date: Fri, 8 Jun 2012 10:48:02 +0200 [thread overview]
Message-ID: <20120608084802.GS30400@pengutronix.de> (raw)
In-Reply-To: <CACKLOr1OShoEnLxs8BP6q2TyZrOH0oCnpbKZJqyAo-yXKck9Zw@mail.gmail.com>
On Fri, Jun 08, 2012 at 09:39:15AM +0200, javier Martin wrote:
> Hi Robert,
>
> On 8 June 2012 09:26, Robert Schwebel <r.schwebel@pengutronix.de> wrote:
> > Hi Javier,
> >
> > On Fri, Jun 08, 2012 at 09:21:13AM +0200, javier Martin wrote:
> >> If you refer to driver in [1] I have some concerns: i.MX27 VPU should
> >> be implemented as a V4L2 mem2mem device since it gets raw pictures
> >> from memory and outputs encoded frames to memory (some discussion
> >> about the subject can be fond here [2]), as Exynos driver from Samsung
> >> does. However, this driver you've mentioned doesn't do that: it just
> >> creates several mapping regions so that the actual functionality is
> >> implemented in user space by a library provided by Freescale, which
> >> regarding i.MX27 it is also GPL.
> >>
> >> What we are trying to do is implementing all the functionality in
> >> kernel space using mem2mem V4L2 framework so that it can be accepted
> >> in mainline.
> >
> > We will work on the VPU driver and it's migration towards a proper
> > mem2mem device very soon, mainly on MX53, but of course MX27 should be
> > taken care of by the same driver.
> >
> > So I'd suggest that we coordinate that work somehow.
>
> Do you plan to provide both encoding and decoding support or just one of them?
We have both encoding and decoding. It works on i.MX51/53, but was
originally written for i.MX27 aswell. I haven't tested i.MX27 for longer
now, so it might or might not work. Find the source here:
git://git.pengutronix.de/git/imx/gst-plugins-fsl-vpu.git
The main difference from the FSL code is that the whole VPU
functionality is in a kernel module which talks (mostly) v4l2. Our next
taks is to convert this into a real mem2mem device, right now it only
works with the included gstreamer plugin. You'll need a small kernel
patch to register the device and to add the clocks.
The gstreamer plugin is in a horrible state, but with the conversion to
mem2mem we hope to get rid of this entirely.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
WARNING: multiple messages have this Message-ID (diff)
From: Sascha Hauer <s.hauer@pengutronix.de>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
kernel@pengutronix.de, Fabio Estevam <festevam@gmail.com>,
linux-media@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>,
Dirk Behme <dirk.behme@googlemail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] Support for H.264/MPEG4 encoder (VPU) in i.MX27.
Date: Fri, 8 Jun 2012 10:48:02 +0200 [thread overview]
Message-ID: <20120608084802.GS30400@pengutronix.de> (raw)
In-Reply-To: <CACKLOr1OShoEnLxs8BP6q2TyZrOH0oCnpbKZJqyAo-yXKck9Zw@mail.gmail.com>
On Fri, Jun 08, 2012 at 09:39:15AM +0200, javier Martin wrote:
> Hi Robert,
>
> On 8 June 2012 09:26, Robert Schwebel <r.schwebel@pengutronix.de> wrote:
> > Hi Javier,
> >
> > On Fri, Jun 08, 2012 at 09:21:13AM +0200, javier Martin wrote:
> >> If you refer to driver in [1] I have some concerns: i.MX27 VPU should
> >> be implemented as a V4L2 mem2mem device since it gets raw pictures
> >> from memory and outputs encoded frames to memory (some discussion
> >> about the subject can be fond here [2]), as Exynos driver from Samsung
> >> does. However, this driver you've mentioned doesn't do that: it just
> >> creates several mapping regions so that the actual functionality is
> >> implemented in user space by a library provided by Freescale, which
> >> regarding i.MX27 it is also GPL.
> >>
> >> What we are trying to do is implementing all the functionality in
> >> kernel space using mem2mem V4L2 framework so that it can be accepted
> >> in mainline.
> >
> > We will work on the VPU driver and it's migration towards a proper
> > mem2mem device very soon, mainly on MX53, but of course MX27 should be
> > taken care of by the same driver.
> >
> > So I'd suggest that we coordinate that work somehow.
>
> Do you plan to provide both encoding and decoding support or just one of them?
We have both encoding and decoding. It works on i.MX51/53, but was
originally written for i.MX27 aswell. I haven't tested i.MX27 for longer
now, so it might or might not work. Find the source here:
git://git.pengutronix.de/git/imx/gst-plugins-fsl-vpu.git
The main difference from the FSL code is that the whole VPU
functionality is in a kernel module which talks (mostly) v4l2. Our next
taks is to convert this into a real mem2mem device, right now it only
works with the included gstreamer plugin. You'll need a small kernel
patch to register the device and to add the clocks.
The gstreamer plugin is in a horrible state, but with the conversion to
mem2mem we hope to get rid of this entirely.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-06-08 8:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 7:21 [RFC] Support for H.264/MPEG4 encoder (VPU) in i.MX27 javier Martin
2012-06-08 7:21 ` javier Martin
[not found] ` <20120608072601.GD30137@pengutronix.de>
2012-06-08 7:39 ` javier Martin
2012-06-08 7:39 ` javier Martin
2012-06-08 7:41 ` Robert Schwebel
2012-06-08 7:41 ` Robert Schwebel
2012-06-08 8:48 ` Sascha Hauer [this message]
2012-06-08 8:48 ` Sascha Hauer
2012-06-08 9:00 ` javier Martin
2012-06-08 9:00 ` javier Martin
2012-06-08 9:02 ` javier Martin
2012-06-08 9:02 ` javier Martin
2012-06-08 9:23 ` Sascha Hauer
2012-06-08 9:23 ` Sascha Hauer
2012-06-08 11:32 ` javier Martin
2012-06-08 11:32 ` javier Martin
2012-06-08 15:25 ` Sascha Hauer
2012-06-08 15:25 ` Sascha Hauer
-- strict thread matches above, loose matches on Subject: below --
2011-09-06 15:07 javier Martin
2011-09-06 15:26 ` Guennadi Liakhovetski
2011-09-07 7:17 ` Robert Schwebel
2011-09-15 17:33 ` Sakari Ailus
2011-09-15 17:48 ` Guennadi Liakhovetski
2011-09-15 22:46 ` Sakari Ailus
2011-09-16 7:49 ` javier Martin
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=20120608084802.GS30400@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.