From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com,
linux-arm-kernel@lists.arm.linux.org.uk, Dan
Subject: Re: [PATCH 2/4 v4] i.MX31: Image Processing Unit DMA and IRQ drivers
Date: Tue, 23 Dec 2008 13:13:00 +0100 [thread overview]
Message-ID: <20081223121300.GL9472@pengutronix.de> (raw)
In-Reply-To: <20081223105006.GE1614@pengutronix.de>
On Tue, Dec 23, 2008 at 11:50:06AM +0100, Sascha Hauer wrote:
> > You mean an output v4l device? I think overlays are handled by framebuffer
> > drivers... But I'm also not quite sure about it, however, handling overlay
> > as another framebuffer seems logical to me.
>
> Well the DMA engine seems to suggest that frames should be passed around
> whereas the framebuffer API only has a single frame. That would fit
> better into the v4l API. Also the IPU can do things like colourspace
> conversion and hw scaling which would fit into the V4L API.
Looks like a candidate for gstreamer on the userspace end. Can it be
decoupled enough to make proper plugins out of it?
> BTW is the overlay framebuffer useful in it's current implementation?
> There seems to be no way to adjust the x/y offset or the blending
> modes.
The API Eric Miao just posted for the PXA looks sane to me.
> > If there are no other problems with v5, could we maybe take it as a
> > basis and then I would submit a patch to reduce the number of IRQs?
>
> Please understand my concerns with this driver. It's a quite complex
> beast and experience shows that once a driver is in the kernel it is
> far more complicated to change it than to do it right the first way.
Especially when it comes to userspace visible things.
> You know that I'm also interested in having a MX31 framebuffer (and
> camera) driver in kernel but I want to make sure that it works
> properly and leaves room for feature enhancements without having to
> refactor the whole driver.
Yup, looks like it would be better to cook it another round instead of
trying to bring in a half-tested driver with brute-force.
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:[~2008-12-23 12:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 13:26 [PATCH 0/4 v4] i.MX31: dmaengine and framebuffer drivers Guennadi Liakhovetski
2008-12-18 13:26 ` [PATCH 1/4 v4] dmaengine: add async_tx_clear_ack() macro Guennadi Liakhovetski
2008-12-18 13:26 ` [PATCH 2/4 v4] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2008-12-18 22:58 ` Sascha Hauer
2008-12-22 11:56 ` Guennadi Liakhovetski
2008-12-22 18:37 ` Sascha Hauer
2008-12-22 20:03 ` Robert Schwebel
2008-12-23 10:09 ` Dmitry Krivoschekov
2008-12-23 10:52 ` Sascha Hauer
2008-12-23 11:32 ` Dmitry Krivoschekov
[not found] ` <4950CC38.3090200@gmail.com>
2008-12-23 12:08 ` Sascha Hauer
2008-12-22 20:10 ` Guennadi Liakhovetski
2008-12-23 10:50 ` Sascha Hauer
2008-12-23 11:21 ` Guennadi Liakhovetski
2008-12-23 12:50 ` Sascha Hauer
2008-12-23 13:14 ` Guennadi Liakhovetski
2008-12-23 14:03 ` Sascha Hauer
2008-12-23 14:55 ` Guennadi Liakhovetski
2008-12-23 16:09 ` Sascha Hauer
2008-12-23 16:33 ` Guennadi Liakhovetski
2008-12-23 17:14 ` Sascha Hauer
2008-12-23 12:13 ` Robert Schwebel [this message]
2008-12-23 12:45 ` Guennadi Liakhovetski
2008-12-23 12:56 ` Sascha Hauer
2008-12-23 12:56 ` Valentin Longchamp
2008-12-18 13:26 ` [PATCH 3/4 v4] i.MX31: framebuffer driver Guennadi Liakhovetski
2008-12-18 13:27 ` [PATCH 4/4 v4] i.MX31: platform bindings and initialisation for IPU and framebuffer drivers Guennadi Liakhovetski
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=20081223121300.GL9472@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=adaplas@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).