linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 7/7] am33xx hwmod data for v3.7 merge window
Date: Thu, 13 Sep 2012 19:34:12 -0700	[thread overview]
Message-ID: <E1TCLlA-0006nz-GV@merlin.infradead.org> (raw)
In-Reply-To: <pull-1347590052-683636>

The following changes since commit 68cb700c59fae6cd539c9dc1e9f2584f671935a0:

  ARM: OMAP1: Move SoC specific headers from plat to mach for omap1 (2012-09-12 18:06:31 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-devel-am33xx-for-v3.7

for you to fetch changes up to 11964f53eb4d9ce59a058be9999d9cfcb1ced878:

  Merge tag 'omap-devel-a2-for-3.7' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into devel-am33xx (2012-09-12 21:29:07 -0700)

----------------------------------------------------------------

>From Paul Walmsley <paul@pwsan.com>:

AM33xx hwmod data and miscellaneous clock and hwmod fixes.  AM33xx
should now boot on mainline after this is applied, according to
Vaibhav.

----------------------------------------------------------------
Tony Lindgren (1):
      Merge tag 'omap-devel-a2-for-3.7' of git://git.kernel.org/.../pjw/omap-pending into devel-am33xx

Vaibhav Hiremath (4):
      ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework
      ARM: OMAP3+: hwmod: Add AM33XX HWMOD data
      ARM: OMAP2+: dpll: Add missing soc_is_am33xx() check for common functions
      ARM: AM33XX: clock: Add dcan clock aliases for device-tree

 arch/arm/mach-omap2/Makefile                 |    1 +
 arch/arm/mach-omap2/clkt_dpll.c              |    4 +-
 arch/arm/mach-omap2/clock33xx_data.c         |    2 +
 arch/arm/mach-omap2/dpll3xxx.c               |    4 +-
 arch/arm/mach-omap2/io.c                     |    2 +
 arch/arm/mach-omap2/omap_hwmod.c             |  178 ++
 arch/arm/mach-omap2/omap_hwmod_33xx_data.c   | 3381 ++++++++++++++++++++++++++
 arch/arm/plat-omap/include/plat/omap_hwmod.h |    1 +
 8 files changed, 3569 insertions(+), 4 deletions(-)
 create mode 100644 arch/arm/mach-omap2/omap_hwmod_33xx_data.c

  parent reply	other threads:[~2012-09-14  2:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pull-1347590052-683636>
2012-09-14  2:34 ` [GIT PULL 3/7] omap gpmc cleanup for v3.7 merge window Tony Lindgren
2012-09-14  2:34 ` [GIT PULL 2/7] omap device changes " Tony Lindgren
2012-09-14  2:34 ` [GIT PULL 5/7] omap sparse irq and local hardware.h cleanup " Tony Lindgren
2012-09-14  2:34 ` [GIT PULL 4/7] omap custom atag removal " Tony Lindgren
2012-09-14  2:34 ` [GIT PULL 6/7] omap makefile and sparse cleanup " Tony Lindgren
2012-09-17  3:08   ` Olof Johansson
2012-09-14  2:34 ` Tony Lindgren [this message]
     [not found] ` <E1TCLkq-0006f8-Qp@merlin.infradead.org>
2012-09-14 17:55   ` [GIT PULL 5/7] omap sparse irq and local hardware.h " Tony Lindgren
     [not found] <pull-1347589125-283636>
2012-09-14  2:18 ` [GIT PULL 7/7] am33xx hwmod data " Tony Lindgren
2012-09-17  3:16   ` Olof Johansson

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=E1TCLlA-0006nz-GV@merlin.infradead.org \
    --to=tony@atomide.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).