linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: benoit.thebaudeau@advansee.com (Benoît Thébaudeau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] DRM: add i.MX IPUv3 base driver
Date: Fri, 24 Aug 2012 16:52:57 +0200 (CEST)	[thread overview]
Message-ID: <806769921.2812305.1345819977325.JavaMail.root@advansee.com> (raw)
In-Reply-To: <1596192785.2810155.1345817566620.JavaMail.root@advansee.com>

Hi Sascha,

On Thu, Jun 14, 09:43:26 EDT 2012, Sascha Hauer wrote:
> The IPU is the Image Processing Unit found on i.MX51/53 SoCs. It
> features several units for image processing, this patch adds support
> for the units needed for Framebuffer support, namely:
> 
> - Display Controller (dc)
> - Display Interface (di)
> - Display Multi Fifo Controller (dmfc)
> - Display Processor (dp)
> - Image DMA Controller (idmac)
> 
> This patch is based on the Freescale driver, but follows a different
> approach. The Freescale code implements logical idmac channels and
> the handling of the subunits is hidden in common idmac code pathes
> in big switch/case statements. This patch instead just provides code
> and resource management for the different subunits. The user, in this
> case the framebuffer driver, decides how the different units play
> together.

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.

> 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?

Would your customers_pengutronix_mx5_master-20120612 tag be the starting point
for these new files? Can it be used as a working solution in the meantime, or
does it have limitations?

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

Matt, I think you also have video support for efikamx, don't you?

Is there a plan to merge all these developments into upstream?

Best regards,
Beno?t

       reply	other threads:[~2012-08-24 14:52 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 ` Benoît Thébaudeau [this message]
2012-08-24 15:58   ` [PATCH 4/5] DRM: add i.MX IPUv3 base driver Dirk Behme
2012-08-27  8:30     ` Sascha Hauer
2012-08-24 17:38   ` Robert Schwebel
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=806769921.2812305.1345819977325.JavaMail.root@advansee.com \
    --to=benoit.thebaudeau@advansee.com \
    --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).