public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] late omap PRCM and hwmod changes for v3.12 merge window
Date: Mon, 26 Aug 2013 07:21:36 -0700	[thread overview]
Message-ID: <pull-1377526896-974252> (raw)

The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:

  Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.12/prcm-signed

for you to fetch changes up to eb8460e01ba632416277ea6d0f6324caa6963e4f:

  Merge tag 'for-v3.12/omap-prcm-hwmod' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.12/prcm (2013-08-26 03:18:43 -0700)

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

OMAP PRCM and hwmod fixes and improvments via Paul Walmsley <paul@pwsan.com>:

Various OMAP PRCM & hwmod fixes and improvements.  Notable changes
include:

- a fix for OMAP4 PLL locking to avoid a bootloader dependency that
  causes nasty log spew on startup

- AM33xx DEBUGSS support fixes in hwmod data

- OMAP5 mailbox support in hwmod data

Basic test logs are here:

http://www.pwsan.com/omap/testlogs/prcm_a_for_v3.12/20130823125002/

Note that the 3530 failure is due to the mysterious transient serial
issue affecting 3530 for several releases now, which causes a log
parsing failure.  PM still seems to work.

----------------------------------------------------------------
Aida Mynzhasova (1):
      ARM: OMAP: TI81XX: add always-on powerdomain for TI81XX

Jon Hunter (1):
      ARM: OMAP2+: Only write the sysconfig on idle when necessary

Lokesh Vutla (1):
      ARM: OMAP: AM33xx: clock: Add RNG clock data

Paul Walmsley (1):
      Merge branches 'hwmod_devel_v3.12', 'prcm_devel_v3.12' and 'am33xx_devel_v3.12' into prcm_a_for_v3.12

Rajendra Nayak (1):
      ARM: OMAP4: clock: Lock PLLs in the right sequence

Suman Anna (1):
      ARM: OMAP5: hwmod data: Add mailbox data

Tony Lindgren (1):
      Merge tag 'for-v3.12/omap-prcm-hwmod' of git://git.kernel.org/.../pjw/omap-pending into omap-for-v3.12/prcm

Vaibhav Hiremath (1):
      ARM: OMAP: AM33XX: hwmod: Add hwmod data for debugSS

 arch/arm/mach-omap2/cclock33xx_data.c       |  5 +++
 arch/arm/mach-omap2/cclock44xx_data.c       | 20 +++++----
 arch/arm/mach-omap2/omap_hwmod.c            |  4 +-
 arch/arm/mach-omap2/omap_hwmod_33xx_data.c  | 69 ++++++++++++++++++++---------
 arch/arm/mach-omap2/omap_hwmod_54xx_data.c  | 42 ++++++++++++++++++
 arch/arm/mach-omap2/powerdomains3xxx_data.c |  8 ++++
 arch/arm/mach-omap2/prcm-common.h           |  1 +
 7 files changed, 118 insertions(+), 31 deletions(-)

             reply	other threads:[~2013-08-26 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26 14:21 Tony Lindgren [this message]
2013-08-26 14:21 ` [GIT PULL 2/2] late dra7xx PRCM and hwmod support for v3.12 merge window Tony Lindgren
     [not found] ` <521b6476.4902310a.1183.6ea6SMTPIN_ADDED_MISSING@mx.google.com>
2013-08-29 23:46   ` Olof Johansson
     [not found] <521b6475.4f2f310a.3f18.45a9SMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-29 23:38 ` [GIT PULL 1/2] late omap PRCM and hwmod changes " 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=pull-1377526896-974252 \
    --to=tony@atomide.com \
    --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