linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] Add device tree support for i.mx51/53 boards
Date: Tue, 2 Aug 2011 15:06:10 +0100	[thread overview]
Message-ID: <20110802140610.GC20071@ponder.secretlab.ca> (raw)
In-Reply-To: <1312267943-25551-1-git-send-email-shawn.guo@linaro.org>

On Tue, Aug 02, 2011 at 02:52:21PM +0800, Shawn Guo wrote:
> Changes since v3:
>  * Fix machine_desc table for ARD matching
>  * Turn the board setup that dt needs into callback
> 
> Changes since v2:
>  * Drop iomuxc device tree support patch
> 
> Changes since v1:
>  * Address comments on v1 given by Grant and Sascha
>  * Add i.mx51 Babbage support
> 
> Shawn Guo (2):
>       arm/mx5: add device tree support for imx53 boards
>       arm/mx5: add device tree support for imx51 babbage

Looks good.

Sascha, assuming you're okay with it, I'd *really* like to ask Arnd to
send this out to Linus immediately.  It may not be perfect, and we may
change the device disable/enable policy, but it is useful enough that
having it in mainline will help developers who want to start hacking
on DT support.

g.

> 
>  .../devicetree/bindings/arm/fsl/boards.txt         |   19 ++
>  arch/arm/boot/dts/imx51-babbage.dts                |  141 +++++++++++
>  arch/arm/boot/dts/imx51.dtsi                       |  203 ++++++++++++++++
>  arch/arm/boot/dts/imx53-ard.dts                    |  158 +++++++++++++
>  arch/arm/boot/dts/imx53-evk.dts                    |  144 ++++++++++++
>  arch/arm/boot/dts/imx53-qsb.dts                    |  148 ++++++++++++
>  arch/arm/boot/dts/imx53-smd.dts                    |  169 ++++++++++++++
>  arch/arm/boot/dts/imx53.dtsi                       |  244 ++++++++++++++++++++
>  arch/arm/mach-mx5/Kconfig                          |   21 ++
>  arch/arm/mach-mx5/Makefile                         |    3 +
>  arch/arm/mach-mx5/board-mx51_babbage.c             |    9 +-
>  arch/arm/mach-mx5/board-mx53_ard.c                 |   12 +-
>  arch/arm/mach-mx5/board-mx53_evk.c                 |    9 +-
>  arch/arm/mach-mx5/board-mx53_loco.c                |    9 +-
>  arch/arm/mach-mx5/board-mx53_smd.c                 |    9 +-
>  arch/arm/mach-mx5/imx51-dt.c                       |  111 +++++++++
>  arch/arm/mach-mx5/imx53-dt.c                       |  127 ++++++++++
>  arch/arm/plat-mxc/include/mach/common.h            |    6 +
>  18 files changed, 1530 insertions(+), 12 deletions(-)
> 
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss

  parent reply	other threads:[~2011-08-02 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02  6:52 [PATCH v4 0/2] Add device tree support for i.mx51/53 boards Shawn Guo
2011-08-02  6:52 ` [PATCH 1/2] arm/mx5: add device tree support for imx53 boards Shawn Guo
2011-08-02  6:52 ` [PATCH 2/2] arm/mx5: add device tree support for imx51 babbage Shawn Guo
2011-08-02 14:06 ` Grant Likely [this message]
2011-08-03  7:45   ` [PATCH v4 0/2] Add device tree support for i.mx51/53 boards Sascha Hauer

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=20110802140610.GC20071@ponder.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).