linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: arnd@atomide.com
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Nicolas Pitre <nico@fluxnic.net>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [GIT PULL] minimal omap4460 support for v3.1 merge window
Date: Sat, 9 Jul 2011 23:56:27 -0700	[thread overview]
Message-ID: <20110710065627.GE5783@atomide.com> (raw)

Hi Arnd,

Please pull minimal omap4460 support from:

git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git 4460

Regards,

Tony


The following changes since commit 48cb1258e8b0f8c81cfb699b42326c5b2147b3f8:
  Tony Lindgren (1):
        Merge branch 'for_3.1/pm-misc' of git://git.kernel.org/.../khilman/linux-omap-pm into devel-cleanup

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git 4460

Aneesh V (2):
      OMAP: ID: introduce chip detection for OMAP4460
      OMAP4: ID: add omap_has_feature for max freq supported

Rajendra Nayak (2):
      OMAP4: PRCM: OMAP4460 specific PRM and CM register bitshifts
      OMAP4: clocks: Update the clock tree with 4460 clock nodes

 arch/arm/mach-omap2/clock44xx_data.c          |   39 ++++++++++++++++++
 arch/arm/mach-omap2/cm-regbits-44xx.h         |   36 +++++++++++++++++
 arch/arm/mach-omap2/id.c                      |   53 ++++++++++++++++++++----
 arch/arm/mach-omap2/prm-regbits-44xx.h        |    8 ++++
 arch/arm/plat-omap/include/plat/clkdev_omap.h |    1 +
 arch/arm/plat-omap/include/plat/clock.h       |    2 +
 arch/arm/plat-omap/include/plat/cpu.h         |   35 +++++++++++++++-
 7 files changed, 162 insertions(+), 12 deletions(-)

             reply	other threads:[~2011-07-10  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-10  6:56 Tony Lindgren [this message]
2011-07-10 19:52 ` [GIT PULL] minimal omap4460 support for v3.1 merge window Tony Lindgren
2011-07-15 10:04   ` Vishwanath Sripathy

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=20110710065627.GE5783@atomide.com \
    --to=tony@atomide.com \
    --cc=arnd@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=tglx@linutronix.de \
    /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).