linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 00/10] OMAP DSS related board changes
Date: Fri, 30 Sep 2011 08:20:43 +0300	[thread overview]
Message-ID: <1317360043.1867.15.camel@deskari> (raw)
In-Reply-To: <20110929175232.GI6324@atomide.com>

On Thu, 2011-09-29 at 10:52 -0700, Tony Lindgren wrote:
> * Tomi Valkeinen <tomi.valkeinen@ti.com> [110925 23:04]:
> > On Tue, 2011-09-20 at 11:18 +0300, Tomi Valkeinen wrote:
> > > Hi Tony,
> > > 
> > > Here is a bunch of board file patches related to DSS. They have all been sent
> > > for review earlier, and are currently in my tree. Some of them depend on DSS
> > > driver changes, so I'd like to keep them there to avoid compilation errors
> > > (these won't compile if you apply them without patches from DSS tree).
> > > 
> > > Can you give your ack for these? Alternatively we can see which of these could
> > > go through your tree and I can make a new set.
> > 
> > Tony, ping. I'd like to get these in for 3.2, as many DSS driver patches
> > depend on some of these.
> 
> Sorry for the delay. Looks like these will conflict with your
> earlier patches I have in the board branch and other cleanup.
> 
> I'll drop the earlier patches from my board branch so you can
> queue all of them:

Ok, I'll add them to dss branch.

> OMAP: Apollon: Port the display driver to new DSS2
> OMAP: H4: Port the display driver to new DSS2
> OMAP: LDP: Port the display driver to new DSS2
> OMAP: 2420SDP: Port the display driver to new DSS2
> OMAP: omap3touchbook: Remove unused lcd stuff
> OMAP: RX51: Remove unused old omapfb stuff
> 
> Your new patches all look OK to me, just please check what we
> have in omap cleanup branch as we don't have all that queud up
> yet in next.

Sure, will do.

> It's likely these will need to be rebased on those, so maybe wait
> a bit with these or adjust them accordingly if possible.
> 
> Also, you might want to start looking into passing the configuration
> from DT instead to avoid the platform init code. Probably the
> panel configuration would be the place to start with that?

I haven't actually looked at DT yet, but one reason I've been writing
and pushing these old omapfb cleanups is to get all omap2+ boards use
the new dss driver, and thus hopefully making DT adaptation easier as I
can (for now) ignore the old omapfb and omap1 boards regarding DT.

But yes, I definitely need to look at DT. Is there a driver to be used
as a sample when looking at DT?

> So for all of them:
> 
> Acked-by: Tony Lindgren <tony@atomide.com>

Thanks.

 Tomi



  reply	other threads:[~2011-09-30  5:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  8:18 [PATCH 00/10] OMAP DSS related board changes Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 01/10] OMAP: DSS2: Change DSI device naming Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 02/10] OMAP4: TWL: Add common omapdss supplies Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 03/10] OMAP: Devkit8000: Change lcd driver to AT070TN83 Tomi Valkeinen
2011-09-20 12:35   ` Thomas Weber
2011-09-20 12:37     ` Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 04/10] OMAP: DSS2: HDMI: use default dividers Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 05/10] OMAP: use dvi panel driver instead of generic-dpi Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 06/10] OMAP: stalker: Remove LCD device from board file Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 07/10] OMAP: Add DDC i2c_bus_num to board files Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 08/10] OMAP: 4430SDP: Remove unneeded lcd config Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 09/10] OMAP4: 4430SDP: Add panel support to board file Tomi Valkeinen
2011-09-20  8:18 ` [PATCH 10/10] OMAP4: 4430SDP: Add picodlp " Tomi Valkeinen
2011-09-26  6:37 ` [PATCH 00/10] OMAP DSS related board changes Tomi Valkeinen
2011-09-29 17:52   ` Tony Lindgren
2011-09-30  5:20     ` Tomi Valkeinen [this message]
2011-10-04  0:32       ` 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=1317360043.1867.15.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --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).