[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160412193128.GO2510@phenom.ffwll.local>
Date: Tue, 12 Apr 2016 21:31:28 +0200
From: Daniel Vetter <daniel@...ll.ch>
To: Liviu Dudau <Liviu.Dudau@....com>
Cc: Dave Airlie <airlied@...il.com>,
Daniel Stone <daniel@...ishbar.org>,
David Brown <David.Brown@....com>,
Brian Starkey <Brian.Starkey@....com>,
devicetree@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
DRI devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [RFC][PATCH 2/2] drm/arm: Add support for Mali Display Processors
On Tue, Apr 12, 2016 at 06:16:54PM +0100, Liviu Dudau wrote:
> On Tue, Apr 12, 2016 at 05:58:11PM +0200, Daniel Vetter wrote:
> > On Fri, Apr 01, 2016 at 05:21:52PM +0100, Liviu Dudau wrote:
> > > Add support for the new family of Display Processors from ARM Ltd.
> > > This commit adds basic support for Mali DP500, DP550 and DP650
> > > parts, with only the display engine being supported at the moment.
> > >
> > > Cc: David Brown <David.Brown@....com>
> > > Cc: Brian Starkey <Brian.Starkey@....com>
> > >
> > > Signed-off-by: Liviu Dudau <Liviu.Dudau@....com>
> >
> > Ok, on 2nd look something puzzling: Where are the
> > drm_encoder/drm_connectors in this driver? Somehow I think just these
> > parts here won't light up a lot ...
>
> The magic of component based drivers, heh :)
>
> On my test system I'm using the NXP TDA19988 HDMI and the driver works
> out of box once the DT describes the proper port/endpoint dance. For
> models/qemu style environment I have a generic DRM encoder driver that I'm
> going to post for review that only reads display timings from DT and behaves
> as if it connected to a real monitor.
I didn't know that magic worked so well already. Seriously impressed, and
happy that it doesn't take anything in addition to make it all just work.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists