linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Tony Lindgren <tony@atomide.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
	Roger Quadros <rogerq@ti.com>, Nishanth Menon <nm@ti.com>,
	Ash Charles <ash@gumstix.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/7] ARM: dts: overo: Add new expansion boards
Date: Thu, 13 Mar 2014 09:29:34 +0100	[thread overview]
Message-ID: <53216C6E.9050706@epfl.ch> (raw)
In-Reply-To: <20140312172247.GC30897@atomide.com>

Hi,

On 03/12/2014 06:22 PM, Tony Lindgren wrote:
> * Florian Vaussard <florian.vaussard@epfl.ch> [140311 05:24]:
>> Hi,
>>
>> This series adds the support for 5 new expansion boards from Gumstix:
>> - Palo43
>> - Gallop43
>> - Chestnut43
>> - Alto35
>> - Summit
>>
>> The 1st patch is a preparatory work, in order to factorize some
>> peripherals that are common to most Gumstix expansion boards. Patch 2
>> adds the support for an accelerometer that is present on most boards.
>>
>> Palo43, Gallop43 and Chestnut43 are all pretty similar. I tested
>> on a Gallop43 (with both OMAP35xx and OMAP36xx Overo).
>>
>> Alto35 is slightly different. Again, I tested with both OMAP35xx and
>> OMAP36xx Overo.
>>
>> Summit is pretty similar to Tobi. I do not have a Summit at hand,
>> but given the similarity with Tobi, it should work fine.
>>
>> To avoid unnecessary duplications, I put all the common stuff for each
>> board inside an omap3-overo-xxx-common.dsti include file. By doing so,
>> I can have minimal SoC-specific omap3-overo-xxx.dts (omap34xx based)
>> and omap3-overo-storm-xxx.dts (omap36xx based) device trees.
>>
>> This series depends on my previous Overo series [1]. A complete testing
>> tree (including the graphics support, soon to be posted) is available
>> at [2].
> 
> Thanks, applying the whole series into omap-for-v3.15/dt-overo.
> As it's this close to the merge window, no guarantees anything
> will get pulled in though.
> 

Thanks! Let's see. Anyway, this will not kill baby bears if it can't
make it into 3.15 :)

Regards,
Florian

      reply	other threads:[~2014-03-13  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 12:20 [PATCH 0/7] ARM: dts: overo: Add new expansion boards Florian Vaussard
2014-03-11 12:20 ` [PATCH 1/7] ARM: dts: overo: Create a file for common Gumstix peripherals Florian Vaussard
2014-03-11 12:20 ` [PATCH 2/7] ARM: dts: overo: Add LIS33DE accelerometer Florian Vaussard
2014-03-11 12:20 ` [PATCH 3/7] ARM: dts: Add support for the Overo Palo43 Florian Vaussard
2014-03-11 12:20 ` [PATCH 4/7] ARM: dts: Add support for the Overo Gallop43 Florian Vaussard
2014-03-11 12:20 ` [PATCH 5/7] ARM: dts: Add support for the Overo Alto35 Florian Vaussard
2014-03-11 12:20 ` [PATCH 6/7] ARM: dts: Add support for the Overo Chestnut43 Florian Vaussard
2014-03-11 12:20 ` [PATCH 7/7] ARM: dts: Add support for the Overo Summit Florian Vaussard
2014-03-12 17:22 ` [PATCH 0/7] ARM: dts: overo: Add new expansion boards Tony Lindgren
2014-03-13  8:29   ` Florian Vaussard [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=53216C6E.9050706@epfl.ch \
    --to=florian.vaussard@epfl.ch \
    --cc=ash@gumstix.com \
    --cc=bcousson@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rogerq@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).