[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <575025DB.9020800@ti.com>
Date: Thu, 2 Jun 2016 15:26:03 +0300
From: Tomi Valkeinen <tomi.valkeinen@...com>
To: <tony@...mide.com>
CC: Peter Ujfalusi <peter.ujfalusi@...com>, <plagnioj@...osoft.com>,
<robdclark@...il.com>, <airlied@...ux.ie>,
<linux-fbdev@...r.kernel.org>, <linux-omap@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<laurent.pinchart@...asonboard.com>, <jsarha@...com>,
<dri-devel@...ts.freedesktop.org>
Subject: Re: [PATCH v2 00/27] fb/drm: omapdss: Clean up the headers and
separate the two stack
Hi Tony,
On 01/06/16 11:35, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - patches (2) added to remove the inclusion of video/omap-panel-data.h when it
> is not needed
> - Transitional patch to create the video/omapfb_dss.h has been changed to copy
> the content of the omapdss.h in one step.
>
> omapfb is deprecated. It will not receive new features, only bug fixes. On the.
> other hand omapdrm is in active development and the fact that both
> implementation (omapfb and omapdrm) is using the same header file
> (video/omapdss.h) makes implementing new features or doing bigger clean ups in
> omapdrm harder and hared as the change should not break omapfb.
>
> To overcome this issue we need to separate the two implementation. This is the
> aim of this series:
> Create platform_data header for omapdss,
> clean up the header usage and dependencies,
> new header file for omapfb stack (video/omapfb_dss.h)
> local omapdss.h header file for omapdrm.
Tony, can you have a look at the arch/arm parts here and give your ack
if they're fine? They should be quite small and display specific, so I
don't see much chance for conflict there.
Tomi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists