From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: <tony@atomide.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>, <plagnioj@jcrosoft.com>,
<robdclark@gmail.com>, <airlied@linux.ie>,
<linux-fbdev@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<laurent.pinchart@ideasonboard.com>, <jsarha@ti.com>,
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 00/27] fb/drm: omapdss: Clean up the headers and separate the two stack
Date: Thu, 2 Jun 2016 15:26:03 +0300 [thread overview]
Message-ID: <575025DB.9020800@ti.com> (raw)
In-Reply-To: <20160601083549.10549-1-peter.ujfalusi@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 1192 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-02 12:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 8:35 [PATCH v2 00/27] fb/drm: omapdss: Clean up the headers and separate the two stack Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 01/27] omapfb: panel-tpo-td028ttec1: Remove legacy boot support Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 02/27] omapfb: panel-nec-nl8048hl11: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 03/27] omapfb: panel-tpo-td043mtea1: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 04/27] omapfb: panel-sharp-ls037v7dw01: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 05/27] omapfb: panel-lgphilips-lb035q02: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 06/27] omapfb: panel-dsi-cm: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 07/27] omapfb: connector-hdmi: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 08/27] omapfb: connector-dvi: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 09/27] omapfb: encoder-tfp410: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 10/27] omapfb: encoder-tpd12s015: No need to include video/omap-panle-data.h Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 11/27] drm/omap: displays: Do not include video/omap-panel-data.h if not needed Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 12/27] omapdss: omap-panel-data.h: Remove struct omap_dss_device declaration Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 13/27] drm/omap: connector-analog-tv: Support only Composite type in legacy boot Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 14/27] omapfb: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 15/27] ARM: OMAP: rx51-video: Do not set TV connector_type Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 16/27] omapdss: omap-panel-data.h: Remove connector_type from atv pdata Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 17/27] ARM/video: omap2: Move omap_display_init declaration to mach-omap2/display.h Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 18/27] drm/omap: Remove reference to pdata->default_device Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 19/27] omapfb: " Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 20/27] video: omapdss: Remove unused members from struct omap_dss_board_info Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 21/27] video/platform_data: omapdss: Create new header file for platform data Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 22/27] ARM: OMAP2: Use the platform_data header for omapdss Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 23/27] omapdss: hdmi audio: Make header file independent of video/omapdss.h Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 24/27] drm/omap: Do not include video/omapdss.h directly in drivers Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 25/27] omapfb: Create new header file for omapfb DSS implementation Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 26/27] [media] omap_vout: Switch to use the video/omapfb_dss.h header file Peter Ujfalusi
2016-06-01 8:35 ` [PATCH v2 27/27] drm/omap: Remove the video/omapdss.h and move it's content to local " Peter Ujfalusi
2016-06-02 12:26 ` Tomi Valkeinen [this message]
2016-06-02 15:23 ` [PATCH v2 00/27] fb/drm: omapdss: Clean up the headers and separate the two stack Tony Lindgren
2016-06-03 10:51 ` Tomi Valkeinen
2016-06-07 5:51 ` Tony Lindgren
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=575025DB.9020800@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=plagnioj@jcrosoft.com \
--cc=robdclark@gmail.com \
--cc=tony@atomide.com \
/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).