linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vaibhav Hiremath <hvaibhav@ti.com>
To: linux-omap@vger.kernel.org
Cc: tony@atomide.com, Vaibhav Hiremath <hvaibhav@ti.com>
Subject: [PATCH-V2 0/3] arm:omap:omap4:Remove hardcoded reg-offs for PWRSTCTRL & PWRSTST
Date: Sun, 8 Jan 2012 15:48:11 +0530	[thread overview]
Message-ID: <1326017894-7632-1-git-send-email-hvaibhav@ti.com> (raw)

This patch series removes the existing hard-coded way of providing
offset to omap4_prminst_xxx API's and instead use offsets
provided in powerdomainsxxxx_data.
Also, hook up AM33XX device support to existing omap4 PRM code.

Background:
==========
PRM module in AM33XX is closer to OMAP4 PRM module, so it complete
sense to reuse all the code from existing OMAP4 implementation.
Having said that, ther is a catch here with respect to AM33XX device,

The register offset in PRM module is not consistent
across (crazy IP integration), for example,

PRM_XXX         PWRSTCTRL PWRSTST RSTCTRL RSTST
===============================================
PRM_PER_MOD:    0x0C,     0x08,   0x00,   0x04
PRM_WKUP_MOD:   0x04,     0x08,   0x00,   0x0C
PRM_MPU_MOD:    0x00,     0x04,   0x08,   NA
PRM_DEVICE_MOD: NA,       NA,     0x00,   0x08

So in order to reuse the existing OMAP4 code, we have to add
seperate entry for register offsets, especially
PWRSTCTRL & PWRSTST.

This patch series is dependent on recently submitted
voltage and powerdomain data patch for AM33xx device -

http://www.mail-archive.com/linux-omap@vger.kernel.org/msg60719.html

Changes from V1:
	- As per Kevin's comment, patch is split into logical
	  commits for ease of review.
	- Added specific comment for cpu_is_xxx check order change.


Vaibhav Hiremath (3):
  arm:omap:omap4: Remove hardcoded reg-offs for PWRSTCTRL & PWRSTST
  arm:omap:omap4: Maintain virtual addr in in _prm_bases table
  arm:omap:omap4: Hook-up am33xx support to existing prm code

 arch/arm/mach-omap2/omap_hwmod.c            |   44 +++++++++++++++++++--------
 arch/arm/mach-omap2/powerdomain.h           |    4 ++
 arch/arm/mach-omap2/powerdomain44xx.c       |   24 +++++++-------
 arch/arm/mach-omap2/powerdomains44xx_data.c |    8 +++++
 arch/arm/mach-omap2/prcm44xx.h              |    4 ++-
 arch/arm/mach-omap2/prminst44xx.c           |   11 ++++---
 6 files changed, 64 insertions(+), 31 deletions(-)


             reply	other threads:[~2012-01-08 10:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08 10:18 Vaibhav Hiremath [this message]
2012-01-08 10:18 ` [PATCH-V2 1/3] arm:omap:omap4: Remove hardcoded reg-offs for PWRSTCTRL & PWRSTST Vaibhav Hiremath
2012-01-10 18:09   ` Kevin Hilman
2012-01-11 16:21     ` Hiremath, Vaibhav
2012-01-17  5:54     ` Hiremath, Vaibhav
2012-01-08 10:18 ` [PATCH-V2 2/3] arm:omap:omap4: Maintain virtual addr in in _prm_bases table Vaibhav Hiremath
2012-01-08 10:18 ` [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code Vaibhav Hiremath
2012-01-10 18:09   ` Kevin Hilman
2012-01-11 16:18     ` Hiremath, Vaibhav
2012-01-23  8:53     ` Hiremath, Vaibhav
2012-01-23 22:35       ` Kevin Hilman
2012-02-01  6:48         ` Hiremath, Vaibhav
2012-02-01 17:33           ` Kevin Hilman
2012-02-02  9:28             ` Hiremath, Vaibhav
2012-02-02 17:59               ` Kevin Hilman
2012-02-02 18:05             ` Hiremath, Vaibhav

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=1326017894-7632-1-git-send-email-hvaibhav@ti.com \
    --to=hvaibhav@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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).