From: Rajendra Nayak <rnayak@ti.com>
To: linux-omap@vger.kernel.org
Cc: khilman@deeprootsystems.com, paul@pwsan.com, b-cousson@ti.com,
Rajendra Nayak <rnayak@ti.com>
Subject: [RFC][PATCH 0/2] Fix prm/cm accessor api's usage on OMAP4
Date: Tue, 10 Aug 2010 20:32:54 +0530 [thread overview]
Message-ID: <1281452576-5705-1-git-send-email-rnayak@ti.com> (raw)
Hi,
This RFC patch series fixes the prm and cm accessor api usage which is
broken today on OMAP4.
OMAP's have always had PRCM split into PRM for power and reset
management and CM for clock management.
In OMAP4 the split (physically) is not very straight forward and
there are instances of clock management control registers in PRM
and vice versa.
However it still makes sense, even on OMAP4 to logically split
PRCM into PRM and CM for better understanding and to avoid adding
additonal complexity in higher level frameworks which rely on the
accessor api;s to do the low level register accesses.
Hence this patch series makes sure that any clock management code can
use the cm_read/write* accessor apis (without knowing the physical split)
and power and reset management code can use prm_read/write*
accessor api;s.
regards,
Rajendra
Rajendra Nayak (2):
OMAP4: PRCM: Add prcm_mpu_base to omap_globals
OMAP4: PRCM: Fix usage of prm/cm accessor api's for OMAP4
arch/arm/mach-omap2/cm.h | 4 +-
arch/arm/mach-omap2/prcm-common.h | 58 +++++++++++++++---------
arch/arm/mach-omap2/prcm.c | 73 ++++++++++++++++++++++++++++--
arch/arm/mach-omap2/prm.h | 4 +-
arch/arm/plat-omap/common.c | 1 +
arch/arm/plat-omap/include/plat/common.h | 1 +
6 files changed, 112 insertions(+), 29 deletions(-)
next reply other threads:[~2010-08-10 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 15:02 Rajendra Nayak [this message]
2010-08-10 15:02 ` [RFC][PATCH 1/2] OMAP4: PRCM: Add prcm_mpu_base to omap_globals Rajendra Nayak
2010-08-10 15:02 ` [RFC][PATCH 2/2] OMAP4: PRCM: Fix usage of prm/cm accessor api's for OMAP4 Rajendra Nayak
2010-08-24 21:39 ` Kevin Hilman
2010-08-25 8:56 ` Nayak, Rajendra
2010-08-25 18:16 ` Kevin Hilman
2010-09-23 14:15 ` Nayak, Rajendra
2010-10-14 18:44 ` Paul Walmsley
2010-10-15 16:07 ` Cousson, Benoit
2010-10-18 22:52 ` Tony Lindgren
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=1281452576-5705-1-git-send-email-rnayak@ti.com \
--to=rnayak@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 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).