From: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
Fabio Estevam <festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/7] i.MX53 IPU + TVE patches
Date: Tue, 09 Apr 2013 09:44:46 +0200 [thread overview]
Message-ID: <1365493486.4023.13.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <20130408174016.GB30036-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
Hi Greg,
Am Montag, den 08.04.2013, 10:40 -0700 schrieb Greg Kroah-Hartman:
> On Mon, Apr 08, 2013 at 06:04:31PM +0200, Philipp Zabel wrote:
> > Hi,
> >
> > the following patches allow to use the integrated Television Encoder
> > (TVEv2) on the i.MX53 SoC as VGA output encoder for the IPU. This is
> > useful for the Freescale i.MX53-QSB and TQ MBa53 boards, which have
> > VGA and DVI-I connectors, respectively.
> >
> > regards
> > Philipp
> >
> > ---
> > drivers/staging/imx-drm/Kconfig | 7 +
> > drivers/staging/imx-drm/Makefile | 1 +
> > drivers/staging/imx-drm/imx-drm-core.c | 15 +-
> > drivers/staging/imx-drm/imx-drm.h | 14 +-
> > drivers/staging/imx-drm/imx-tve.c | 755 ++++++++++++++++++++++++++++
> > drivers/staging/imx-drm/ipu-v3/imx-ipu-v3.h | 3 +
> > drivers/staging/imx-drm/ipu-v3/ipu-dc.c | 55 +-
> > drivers/staging/imx-drm/ipu-v3/ipu-di.c | 100 +++-
> > drivers/staging/imx-drm/ipuv3-crtc.c | 11 +-
> > 9 files changed, 932 insertions(+), 29 deletions(-)
>
> That's a lot of new features being added here, yet no work seems to be
> happening to move this out of the staging tree. What is left to do
> here, and why isn't that being worked on first, before stuff like this?
the IPU code could still use a bit of testing, and I hope adding
features like VGA output on common development boards will increase the
amount of scrutiny this code will get.
I expect the structure of the IPU drivers to change when the common
display framework gets introduced at last, also requiring changes to the
device tree bindings, and I'm a bit reluctant to push for mainline
proper while the bindings are still not clear.
regards
Philipp
next prev parent reply other threads:[~2013-04-09 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 16:04 [PATCH 0/7] i.MX53 IPU + TVE patches Philipp Zabel
[not found] ` <1365437078-22579-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-04-08 16:04 ` [PATCH 1/7] staging: drm/imx: ipu-dc: add 24-bit GBR support to DC Philipp Zabel
2013-04-08 16:04 ` [PATCH 2/7] staging: drm/imx: ipuv3-crtc: use external clock for TV Encoder Philipp Zabel
2013-04-08 16:04 ` [PATCH 3/7] staging: drm/imx: ipu-di: add comments explaining signal generator configuration Philipp Zabel
2013-04-08 16:04 ` [PATCH 4/7] staging: drm/imx: Add support for VGA via TVE on i.MX53 Philipp Zabel
2013-04-08 16:04 ` [PATCH 5/7] staging: drm/imx: ipu-dc: add WCLK/WRG opcodes Philipp Zabel
2013-04-08 16:04 ` [PATCH 6/7] staging: drm/imx: ipu-dc: force black output during blanking Philipp Zabel
2013-04-08 16:04 ` [PATCH 7/7] staging: drm/imx: Add support for Television Encoder (TVEv2) Philipp Zabel
[not found] ` <1365437078-22579-8-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-04-09 12:55 ` Shawn Guo
2013-04-08 17:40 ` [PATCH 0/7] i.MX53 IPU + TVE patches Greg Kroah-Hartman
[not found] ` <20130408174016.GB30036-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-04-09 7:44 ` Philipp Zabel [this message]
2013-04-09 23:15 ` Greg Kroah-Hartman
[not found] ` <20130409231523.GA15722-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-04-11 9:04 ` [PATCH] staging: drm/imx: update TODO file Sascha Hauer
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=1365493486.4023.13.camel@pizza.hi.pengutronix.de \
--to=p.zabel-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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).