From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] DRM: add i.MX IPUv3 base driver
Date: Fri, 24 Aug 2012 19:38:08 +0200 [thread overview]
Message-ID: <20120824173808.GN31821@pengutronix.de> (raw)
In-Reply-To: <806769921.2812305.1345819977325.JavaMail.root@advansee.com>
Beno?t,
On Fri, Aug 24, 2012 at 04:52:57PM +0200, Beno?t Th?baudeau wrote:
> What is the status of this series, and especially of this patch, as to
> its integration into upstream? At some point, you were talking about
> pushing it to staging, but since things don't seem to have evolved.
Things are making progress. The intention is to get the base patches
into staging; however, the holiday season made the progress a bit slow
recently.
> > The IPU has other units missing in this patch:
> >
> > - CMOS Sensor Interface (csi)
> > - Video Deinterlacer (vdi)
> > - Sensor Multi FIFO Controler (smfc)
> > - Image Converter (ic)
> > - Image Rotator (irt)
> >
> > So expect more files to come in this directory.
>
> Do you have a schedule for that? Are you waiting for more customer
> projects at Pengutronix to do that?
We don't have a fixed schedule; things make progress according to what
our projects make possible. The more customers we get behind this
effort, the more time we can spent on it.
- CSI is running on MX6 here
- Deinterlacer is WIP on MX53
- VPU was posted today, based on the Vista Silicon patches; we can do
encoding and decoding, but not in all possible formats
- scaler works here
- We have a m2m plugin for GStreamer (which needs polishing as well, but
works)
> That would be great to finally have full IPU/VPU/GPU support for i.MX5
> into upstream. As you already know, Linaro also have some video
> support for i.MX5 in this head:
> http://git.linaro.org/gitweb?p=landing-teams/working/freescale/kernel.git;a=shortlog;h=refs/heads/lt-3.2-imx5
That's quite an old tree... especially the port to 3.5 made a lot of
headache until all the oftree and clock issues were solved. However,
it's still good for reference.
> Is there a plan to merge all these developments into upstream?
>From our side: definitely! Everything is posted here on the lists when
it's in a state that we think we can show it to you folks.
rsc
--
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-08-24 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1596192785.2810155.1345817566620.JavaMail.root@advansee.com>
2012-08-24 14:52 ` [PATCH 4/5] DRM: add i.MX IPUv3 base driver Benoît Thébaudeau
2012-08-24 15:58 ` Dirk Behme
2012-08-27 8:30 ` Sascha Hauer
2012-08-24 17:38 ` Robert Schwebel [this message]
2012-08-24 18:00 ` Matt Sealey
2012-08-24 18:31 ` Russell King - ARM Linux
2012-06-14 13:43 [PATCH, RFC] i.MX DRM support Sascha Hauer
2012-06-14 13:43 ` [PATCH 4/5] DRM: add i.MX IPUv3 base driver Sascha Hauer
2012-06-22 6:04 ` Shawn Guo
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=20120824173808.GN31821@pengutronix.de \
--to=r.schwebel@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 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).