devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	grant.likely@secretlab.ca,
	Enric Balletbo i Serra <eballetbo@gmail.com>,
	Ezequiel Garcia <elezegarcia@gmail.com>,
	Enrico Butera <ebutera@gmail.com>,
	Matthias Brugger <matthias.bgg@googlemail.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] ARM/dts: omap3: Add DT support for IGEP devices
Date: Wed, 12 Dec 2012 09:25:10 +0100	[thread overview]
Message-ID: <CAAwP0s2qXuJzwEh-AVORbPApr6XT0JAfsFjrxKDvXArqYk0qXQ@mail.gmail.com> (raw)
In-Reply-To: <1354538503-22671-1-git-send-email-javier.martinez@collabora.co.uk>

On Mon, Dec 3, 2012 at 1:41 PM, Javier Martinez Canillas
<javier.martinez@collabora.co.uk> wrote:
> IGEP technology devices are TI OMAP3 SoC based industrial embedded
> and computer-on-module boards. This patch-set adds initial device
> tree support for these devices.
>
> The device trees allows to boot from an MMC and are working all the
> components that already have device tree support on OMAP3 SoCs:
>
> - MMC/SD
> - UARTs
> - GPIO LEDs
> - TWL4030 codec audio
> - pinmux/pinconf pinctrl
>
> Some peripheral are still not working such as Flash storage and
> Ethernet but support for these will also be included once the
> OMAP GPMC device tree binding patches land on mainline.
>
> This is a v3 of the patch-set that solves issues pointed out by
> Enric Balletbo and Benoit Cousson.
>
> The patch-set is composed of the following patches:
>
> [PATCH v3 1/3] ARM/dts: omap3: Add generic DT support for IGEP devices
> [PATCH v3 2/3] ARM/dts: omap3: Add support for IGEPv2 board
> [PATCH v3 3/3] ARM/dts: omap3: Add support for IGEP COM Module
>
> Best regards,
> Javier
> --

Hi Benoit and Tony,

Any comments on these?

Best regards,
Javier

  parent reply	other threads:[~2012-12-12  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 12:41 [PATCH v3 0/3] ARM/dts: omap3: Add DT support for IGEP devices Javier Martinez Canillas
2012-12-03 12:41 ` [PATCH v3 1/3] ARM/dts: omap3: Add generic " Javier Martinez Canillas
     [not found] ` <1354538503-22671-1-git-send-email-javier.martinez-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2012-12-03 12:41   ` [PATCH v3 2/3] ARM/dts: omap3: Add support for IGEPv2 board Javier Martinez Canillas
2012-12-03 12:41 ` [PATCH v3 3/3] ARM/dts: omap3: Add support for IGEP COM Module Javier Martinez Canillas
2012-12-12  8:25 ` Javier Martinez Canillas [this message]
2012-12-12 10:11   ` [PATCH v3 0/3] ARM/dts: omap3: Add DT support for IGEP devices Benoit Cousson
2012-12-12 11:42     ` Javier Martinez Canillas

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=CAAwP0s2qXuJzwEh-AVORbPApr6XT0JAfsFjrxKDvXArqYk0qXQ@mail.gmail.com \
    --to=martinez.javier@gmail.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=eballetbo@gmail.com \
    --cc=ebutera@gmail.com \
    --cc=elezegarcia@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=matthias.bgg@googlemail.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).