linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, <plagnioj@jcrosoft.com>,
	<robdclark@gmail.com>, <airlied@linux.ie>, <tony@atomide.com>
Cc: <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 00/26] fb/drm: omapdss: Clean up the headers and separate the two stack
Date: Mon, 30 May 2016 17:26:38 +0300	[thread overview]
Message-ID: <574C4D9E.6030307@ti.com> (raw)
In-Reply-To: <20160530114258.30879-1-peter.ujfalusi@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 1409 bytes --]

Hi Peter, Tony,

On 30/05/16 14:42, Peter Ujfalusi wrote:
> Hi,
> 
> 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.
> 
> To generate the set I have used:
> git format-patch -C20 --find-copies-harder

Yeah, you need to drop -C20 to get a bit saner "renames" in the patches =).

But otherwise, looks good.

One thing which is not strictly required, but I think should be added,
is cleaning up the omap-panel-data.h from the drm side. There are many
panels including the file, but not using it.

I don't think there's any sane way to split this series into different
subsystems. So I think we should merge this via drm tree.

Tony, can we get acks from you for the mach-omap2 patches? Do you think
there's anything there that could cause bigger conflicts?

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-05-30 14:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 11:42 [PATCH 00/26] fb/drm: omapdss: Clean up the headers and separate the two stack Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 01/26] omapfb: panel-tpo-td028ttec1: Remove legacy boot support Peter Ujfalusi
2016-05-30 11:56   ` Belisko Marek
2016-05-30 12:35     ` Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 02/26] omapfb: panel-nec-nl8048hl11: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 03/26] omapfb: panel-tpo-td043mtea1: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 04/26] omapfb: panel-sharp-ls037v7dw01: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 05/26] omapfb: panel-lgphilips-lb035q02: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 06/26] omapfb: panel-dsi-cm: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 07/26] omapfb: connector-hdmi: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 08/26] omapfb: connector-dvi: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 09/26] omapfb: encoder-tfp410: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 10/26] omapdss: omap-panel-data.h: Remove struct omap_dss_device declaration Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 11/26] drm/omap: connector-analog-tv: Support only Composite type in legacy boot Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 12/26] omapfb: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 13/26] ARM: OMAP: rx51-video: Do not set TV connector_type Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 14/26] omapdss: omap-panel-data.h: Remove connector_type from atv pdata Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 15/26] ARM/video: omap2: Move omap_display_init declaration to mach-omap2/display.h Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 16/26] drm/omap: Remove reference to pdata->default_device Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 17/26] omapfb: " Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 18/26] video: omapdss: Remove unused members from struct omap_dss_board_info Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 19/26] video/platform_data: omapdss: Create new header file for platform data Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 20/26] ARM: OMAP2: Use the platform_data header for omapdss Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 21/26] omapdss: hdmi audio: Make header file independent of video/omapdss.h Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 22/26] drm/omap: Do not include video/omapdss.h directly in drivers Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 23/26] omapfb: Create new header file for omapfb DSS implementation Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 24/26] [media] omap_vout: Switch to use the video/omapfb_dss.h header file Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 25/26] omapfb: Copy video/omapdss.h content to video/omapfb_dss.h Peter Ujfalusi
2016-05-30 11:42 ` [PATCH 26/26] drm/omap: Remove the video/omapdss.h and move it's content to local header file Peter Ujfalusi
2016-05-30 14:26 ` Tomi Valkeinen [this message]

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=574C4D9E.6030307@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).