public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Nicolas Pitre <nicolas.pitre@linaro.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Russell King <rmk@arm.linux.org.uk>
Subject: [GIT PULL] arm-soc new board support for 3.1
Date: Wed, 27 Jul 2011 01:01:44 +0200	[thread overview]
Message-ID: <5818290.TCY0zMWmbr@wuerfel> (raw)
In-Reply-To: <2178768.MnKF3D4aeP@wuerfel>

Hi Linus,

This adds support for new boards in the TI omap and samsung s3c platforms.
These platforms are still a long way from being able to add support for
new boards just with a device tree instead of a board file, but it's
clear from the work going into these platforms that the maintainers
are actively working on changing that.

Once we get to the point that the platforms can describe a board using
a device tree, we will start removing existing board files and no longer
allow new ones. Until then, my feeling is that we need to allow additional
boards to be added when they are clean enough and work is proceeding on
obsoleting them.

	Arnd

The following changes since commit ba5b56cb3e3d2cab73d4fee9a022bb69462a8cd9:

  Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client (2011-07-26 13:38:50 -0700)

are available in the git repository at:

  git+ssh://master.kernel.org/pub/scm/linux/kernel/git/arm/linux-arm-soc.git/ next/board

Ambresh K (1):
      OMAP4: DMTIMER: enable autoidle mode

Ameya Palande (1):
      omap: rx51: Platform support for lp5523 led chip

Arnd Bergmann (2):
      Merge branch 'omap/board' of git+ssh://master.kernel.org/.../arm/linux-arm-soc into next/board
      Merge branch 'next-samsung-board' of git://git.kernel.org/.../kgene/linux-samsung into next/board

Charulatha V (1):
      omap: ZOOM: QUART: Request reset GPIO

Daniel Mack (1):
      omap: Overo: remove duplicate call to overo_ads7846_init()

Igor Grinberg (3):
      arm: omap3: cm-t35: minor comments fixes
      arm: omap3: cm-t35: fix slow path warning
      arm: omap3: cm-t35: add support for cm-t3730

Joel A Fernandes (1):
      OMAP3: beagle: add support for beagleboard xM revision C

Julia Lawall (1):
      arch/arm/mach-omap2/clock.c: add missing clk_put

Kalle Jokiniemi (1):
      OMAP3: rx-51: Add full regulator definitions

Mark Brown (5):
      ARM: S3C64XX: Initial support for Wolfson/Simtec Cragganmore/Banff
      ARM: S3C64XX: Refresh Cragganmore support
      ARM: S3C64XX: Configure supplies for all Cragganmore regulators

Ohad Ben-Cohen (2):
      omap: iovmm: s/sg_dma_len(sg)/sg->length/
      OMAP4: iommu: fix clock name

Shubhrajyoti Datta (1):
      OMAP4: Keyboard: Mux changes in the board file

Silesh C V (2):
      omap: HSMMC: Fix GPIO muxing
      omap: 4430SDP: Register the card detect GPIO properly

Suman Anna (1):
      omap: iommu: fix pte programming

Tony Lindgren (2):
      Merge branch 'iommu-for-tony' of git://github.com/ohadbc/omap-iommu into devel-fixes
      Merge branch 'cleanup-part-2' into devel-board

Vishal Mahaveer (1):
      omap: blaze: add mmc5/wl1283 device support

 arch/arm/mach-omap2/Kconfig                    |    6 +-
 arch/arm/mach-omap2/board-4430sdp.c            |  148 +++++-
 arch/arm/mach-omap2/board-cm-t35.c             |   95 ++-
 arch/arm/mach-omap2/board-omap3beagle.c        |   78 ++-
 arch/arm/mach-omap2/board-overo.c              |    1 -
 arch/arm/mach-omap2/board-rx51-peripherals.c   |  135 ++++
 arch/arm/mach-omap2/board-zoom-debugboard.c    |    9 +
 arch/arm/mach-omap2/clock.c                    |    1 +
 arch/arm/mach-omap2/devices.c                  |    3 +-
 arch/arm/mach-omap2/hsmmc.c                    |    7 +-
 arch/arm/mach-omap2/iommu2.c                   |    4 +-
 arch/arm/mach-omap2/omap-iommu.c               |    2 +-
 arch/arm/mach-s3c64xx/Kconfig                  |   23 +
 arch/arm/mach-s3c64xx/Makefile                 |    1 +
 arch/arm/mach-s3c64xx/include/mach/irqs.h      |    4 +-
 arch/arm/mach-s3c64xx/mach-crag6410.c          |  774 ++++++++++++++++++++++++
 arch/arm/plat-omap/dmtimer.c                   |    4 +-
 arch/arm/plat-omap/include/plat/omap4-keypad.h |    3 +-
 arch/arm/plat-omap/include/plat/uncompress.h   |    1 +
 arch/arm/plat-omap/iovmm.c                     |    6 +-
 20 files changed, 1233 insertions(+), 72 deletions(-)


  reply	other threads:[~2011-07-26 23:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 22:24 [GIT PULL] arm-soc new SOCs for 3.1 Arnd Bergmann
2011-07-26 22:31 ` [GIT PULL] arm-soc bug fixes (part 2) " Arnd Bergmann
2011-07-26 22:36   ` [GIT PULL] arm-soc cross-platform cleanups " Arnd Bergmann
2011-07-26 23:01     ` Arnd Bergmann [this message]
2011-07-26 23:25       ` [GIT PULL] arm-soc new features (part 1/2) " Arnd Bergmann
2011-07-26 23:36         ` [GIT PULL] arm-soc new features (part 2/2) " Arnd Bergmann
2011-07-27  0:51           ` Linus Torvalds
2011-07-27 15:07             ` Arnd Bergmann

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=5818290.TCY0zMWmbr@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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