All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: paul@pwsan.com, rnayak@ti.com
Cc: linux-omap@vger.kernel.org, Benoit Cousson <b-cousson@ti.com>
Subject: [PATCH 0/3] OMAP4: PRCM fixes
Date: Thu, 23 Jun 2011 18:45:41 +0200	[thread overview]
Message-ID: <1308847544-2322-1-git-send-email-b-cousson@ti.com> (raw)

Hi Paul & Rajendra,

Here are a couple of fixes on PRCM header files and powerdomain data.

The series is based on v3.0-rc4 and tested on OMAP4430 ES2.1 + SDP.

The patches are available here:
git://gitorious.org/omap-pm/linux.git for_3.0.1/1_prcm_files_fixes

Regards,
Benoit


Benoit Cousson (3):
  OMAP4: pcrm: Fix errors in few defines name
  OMAP4: prm: Remove wrong clockdomain offsets
  OMAP4: powerdomain data: Fix core mem states and missing cefuse flag

 arch/arm/mach-omap2/cm1_44xx.h              |   28 +++++++++++-----------
 arch/arm/mach-omap2/cm2_44xx.h              |   23 ++++++++---------
 arch/arm/mach-omap2/powerdomains44xx_data.c |   25 ++++++++++---------
 arch/arm/mach-omap2/prm44xx.h               |   34 ++++++++------------------
 4 files changed, 49 insertions(+), 61 deletions(-)


             reply	other threads:[~2011-06-23 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 16:45 Benoit Cousson [this message]
2011-06-23 16:45 ` [PATCH 1/3] OMAP4: pcrm: Fix errors in few defines name Benoit Cousson
2011-06-30 23:02   ` Paul Walmsley
2011-06-23 16:45 ` [PATCH 2/3] OMAP4: prm: Remove wrong clockdomain offsets Benoit Cousson
2011-06-30 23:12   ` Paul Walmsley
2011-06-23 16:45 ` [PATCH 3/3] OMAP4: powerdomain data: Fix core mem states and missing cefuse flag Benoit Cousson
2011-06-30 23:48   ` Paul Walmsley
2011-07-01 10:09     ` Cousson, Benoit
2011-06-30 23:55 ` [PATCH 0/3] OMAP4: PRCM fixes Paul Walmsley

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=1308847544-2322-1-git-send-email-b-cousson@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=rnayak@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.