All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	archit@ti.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, s-guiriec@ti.com
Subject: Re: [PATCH 0/6] OMAPDSS: enable DSS for Panda & SDP with devtree
Date: Wed, 7 Nov 2012 13:34:50 -0800	[thread overview]
Message-ID: <20121107213450.GL6801@atomide.com> (raw)
In-Reply-To: <509A3EE2.1080500@ti.com>

* Benoit Cousson <b-cousson@ti.com> [121107 03:00]:
> On 11/07/2012 02:04 AM, Tony Lindgren wrote:
> > * Tomi Valkeinen <tomi.valkeinen@ti.com> [121105 05:16]:
> >> Hi,
> >>
> >> OMAPDSS device tree support is still some way in the future. Tony has requested
> >> to get DSS working for Panda & SDP boards with DT kernel, so that we'll have
> >> fully working boards with DT.
> >>
> >> This series makes a few hacks to get a working display on OMAP4 Panda and SDP
> >> boards. The idea is to setup the omapdss with the non-DT method, creating the
> >> omapdss devices and passing platform data to them. This setup code is called
> >> from board-generic for Panda and SDP boards.
> >>
> >> There was one problem with this approach: omapdss cannot get regulators using
> >> the omapdss's names fro the regulators. Thus there's a hack patch to get the
> >> regulators using the OMAP4 "native" regulator names, thus circumventing the
> >> problem.
> >>
> >> Tony, if these look good, how do you want to merge these? There are three parts
> >> here, and I think they can be merged independently if so wished:
> >>
> >> * .dts changes for the pinmuxing (2 patches)
> > 
> > Let's let Benoit queue these.
> 
> Done. I'll send you the pull-request tomorrow in case some more DTS
> patches are coming.

OK thanks, I'll apply 3-6 to omap-for-v3.8/board branch.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] OMAPDSS: enable DSS for Panda & SDP with devtree
Date: Wed, 7 Nov 2012 13:34:50 -0800	[thread overview]
Message-ID: <20121107213450.GL6801@atomide.com> (raw)
In-Reply-To: <509A3EE2.1080500@ti.com>

* Benoit Cousson <b-cousson@ti.com> [121107 03:00]:
> On 11/07/2012 02:04 AM, Tony Lindgren wrote:
> > * Tomi Valkeinen <tomi.valkeinen@ti.com> [121105 05:16]:
> >> Hi,
> >>
> >> OMAPDSS device tree support is still some way in the future. Tony has requested
> >> to get DSS working for Panda & SDP boards with DT kernel, so that we'll have
> >> fully working boards with DT.
> >>
> >> This series makes a few hacks to get a working display on OMAP4 Panda and SDP
> >> boards. The idea is to setup the omapdss with the non-DT method, creating the
> >> omapdss devices and passing platform data to them. This setup code is called
> >> from board-generic for Panda and SDP boards.
> >>
> >> There was one problem with this approach: omapdss cannot get regulators using
> >> the omapdss's names fro the regulators. Thus there's a hack patch to get the
> >> regulators using the OMAP4 "native" regulator names, thus circumventing the
> >> problem.
> >>
> >> Tony, if these look good, how do you want to merge these? There are three parts
> >> here, and I think they can be merged independently if so wished:
> >>
> >> * .dts changes for the pinmuxing (2 patches)
> > 
> > Let's let Benoit queue these.
> 
> Done. I'll send you the pull-request tomorrow in case some more DTS
> patches are coming.

OK thanks, I'll apply 3-6 to omap-for-v3.8/board branch.

Regards,

Tony

  reply	other threads:[~2012-11-07 21:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 13:14 [PATCH 0/6] OMAPDSS: enable DSS for Panda & SDP with devtree Tomi Valkeinen
2012-11-05 13:14 ` Tomi Valkeinen
2012-11-05 13:14 ` [PATCH 1/6] ARM/dts: omap4-panda: Add pinmux configuration for HDMI Tomi Valkeinen
2012-11-05 13:14   ` Tomi Valkeinen
2012-11-05 13:17   ` Tomi Valkeinen
2012-11-05 13:17     ` Tomi Valkeinen
2012-11-06  5:24     ` Ricardo Neri
2012-11-06  5:24       ` Ricardo Neri
2012-11-05 17:43   ` Benoit Cousson
2012-11-05 17:43     ` Benoit Cousson
2012-11-07 10:56   ` Benoit Cousson
2012-11-07 10:56     ` Benoit Cousson
2012-11-13 19:10   ` Ricardo Neri
2012-11-13 19:10     ` Ricardo Neri
2012-11-14  7:39     ` Tomi Valkeinen
2012-11-14  7:39       ` Tomi Valkeinen
2012-11-05 13:14 ` [PATCH 2/6] ARM/dts: omap4-sdp: " Tomi Valkeinen
2012-11-05 13:14   ` Tomi Valkeinen
2012-11-07 10:57   ` Benoit Cousson
2012-11-07 10:57     ` Benoit Cousson
2012-11-05 13:14 ` [PATCH 3/6] OMAPDSS: HACK: look for regulators with omap4 names Tomi Valkeinen
2012-11-05 13:14   ` Tomi Valkeinen
2012-11-05 13:14 ` [PATCH 4/6] OMAP: panda: move display init from board file to dss-common.c Tomi Valkeinen
2012-11-05 13:14   ` Tomi Valkeinen
2012-11-05 13:14 ` [PATCH 5/6] OMAP: omap4sdp: " Tomi Valkeinen
2012-11-05 13:14   ` Tomi Valkeinen
2012-11-05 13:14 ` [PATCH 6/6] OMAP: board-generic: enable DSS for panda & sdp boards Tomi Valkeinen
2012-11-05 13:14   ` Tomi Valkeinen
2012-11-07  1:04 ` [PATCH 0/6] OMAPDSS: enable DSS for Panda & SDP with devtree Tony Lindgren
2012-11-07  1:04   ` Tony Lindgren
2012-11-07 10:58   ` Benoit Cousson
2012-11-07 10:58     ` Benoit Cousson
2012-11-07 21:34     ` Tony Lindgren [this message]
2012-11-07 21:34       ` 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=20121107213450.GL6801@atomide.com \
    --to=tony@atomide.com \
    --cc=archit@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=s-guiriec@ti.com \
    --cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.