linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	Enric Balletbo i Serra <eballetbo@gmail.com>,
	bcousson@baylibre.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: OMAP2+: pdata-quirks: add legacy display init for IGEPv2 board
Date: Wed, 09 Oct 2013 09:54:56 +0200	[thread overview]
Message-ID: <52550BD0.1060901@collabora.co.uk> (raw)
In-Reply-To: <52550A28.4060508@ti.com>

On 10/09/2013 09:47 AM, Tomi Valkeinen wrote:
> On 09/10/13 10:44, Javier Martinez Canillas wrote:
> 
>> I can't do it yet because the two are still needed for different boot paths.
>> Once the board DTS has all the hardware support that is currently available on
>> the board file I'll delete the board file but until then I can't remove anything
>> from the legacy code since that is what users are using right now.
> 
> Yes, right, I meant that move the code from the board file to
> dss_common.c, and call the same display init code from both the board
> file and from the quirks system.
>

Sorry I misunderstood and yes you are right. I'll remove it from the board file
and use the info in dss_common.c.

If Tony drop the patch I can send a new version that does this or if he already
sent a pull request I can do it as an incremental patch.

>  Tomi
> 
> 

Thanks a lot and best regards,
Javier


      reply	other threads:[~2013-10-09  7:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05  2:51 [PATCH 1/1] ARM: OMAP2+: pdata-quirks: add legacy display init for IGEPv2 board Javier Martinez Canillas
2013-10-08 21:11 ` Tony Lindgren
2013-10-09  6:02   ` Tomi Valkeinen
2013-10-09  7:36     ` Javier Martinez Canillas
2013-10-09 14:52       ` Tony Lindgren
2013-10-09  6:00 ` Tomi Valkeinen
2013-10-09  7:44   ` Javier Martinez Canillas
2013-10-09  7:47     ` Tomi Valkeinen
2013-10-09  7:54       ` Javier Martinez Canillas [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=52550BD0.1060901@collabora.co.uk \
    --to=javier.martinez@collabora.co.uk \
    --cc=bcousson@baylibre.com \
    --cc=eballetbo@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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).