[PATCH 4/5] fb: Add DCU framebuffer driver for Vybrid VF610 platform
B18965 at freescale.com
Tue Aug 6 03:20:58 EDT 2013
> Am Montag, den 05.08.2013, 15:09 +0200 schrieb Robert Schwebel:
> > On Mon, Aug 05, 2013 at 09:51:40AM +0000, Wang Huan-B18965 wrote:
> > > > On Fri, Jul 12, 2013 at 02:07:55PM +0800, Alison Wang wrote:
> > > > > The Display Controller Unit (DCU) module is a system master
> > > > > fetches graphics stored in internal or external memory and
> > > > > displays them on a TFT LCD panel. A wide range of panel sizes
> > > > > supported and the timing of the interface signals is highly
> > > > > Graphics are read directly from memory and then blended in
> > > > > real-time, which allows for dynamic content creation with
> > > > > minimal CPU
> > > > intervention.
> > > >
> > > > Only a review of the code inline.
> > > >
> > > > Maybe the real question is whether we want to introduce another
> > > > framebuffer driver at all instead of making it a DRM driver.
> > > [Alison Wang] I think DCU module is more suitable to be designed as
> a framebuffer driver than a DRM driver. Just like DIU framebuffer
> driver for PowerPC.
> > We looked at the Vybrid datasheet and it's DCU section last week, and
> > with its 64 planes, the controller really wants to get a DRM driver.
> Exactly, with it's extensive hardware composition capabilities the
> controller begs for being driven by a proper DRM driver. There is no
> way in fbdev to properly support all those hardware planes without
> introducing a lot of non standard ioctls, which in turn will force you
> into writing a lot of custom userspace code instead of running proven
> technology that sits on top of KMS.
> Doing things in DRM might be slightly more work for the initial bring
> up, but will pay off in the long run when you are going to really use
> the hardware caps of the controller.
[Alison Wang] Thanks for your comments and explanations. I understand your considerations.
In DCU module, there are 64 graphics layers, but the maximum source layers for blending of each pixel is only 6. The fb driver could satisfy the current application requirements.
So I will push out this fb driver first, and then I will add a DRM driver for more advanced requirements.
Do you have more comments?
More information about the linux-arm-kernel