From: govindraj.raja@ti.com (Govindraj.R)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] ARM: omap_hwmod: add api to enable/disable module level wakeup
Date: Tue, 24 Apr 2012 19:39:10 +0530 [thread overview]
Message-ID: <1335276552-24340-1-git-send-email-govindraj.raja@ti.com> (raw)
From: "Govindraj.R" <govindraj.raja@ti.com>
On omap2/3 module level wakeup is handled using PM_WKEN registers.
Expand the hwmod framework to handle the module level wakeup enable
registers.
Tested on Beagle-xm by enabling and disabling uart wakeups from sysfs
Series depends on following patches for testing.
http://marc.info/?l=linux-omap&m=133527588923598&w=2
http://marc.info/?l=linux-omap&m=133518614022144&w=2
Cc: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Govindraj.R (2):
ARM: OMAP2+: omap_hwmod: Add api to enable/disable module level
wakeup events
ARM: omap3: pm: Remove uart module level wakeup configurations
arch/arm/mach-omap2/omap_hwmod.c | 22 ++++++++++++++++++++++
arch/arm/mach-omap2/pm34xx.c | 14 +++++---------
arch/arm/mach-omap2/prm2xxx_3xxx.c | 16 ++++++++++++++++
arch/arm/mach-omap2/prm2xxx_3xxx.h | 9 +++++++++
4 files changed, 52 insertions(+), 9 deletions(-)
--
1.7.9
next reply other threads:[~2012-04-24 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 14:09 Govindraj.R [this message]
2012-04-24 14:09 ` [PATCH v3 1/2] ARM: OMAP2+: omap_hwmod: Add api to enable/disable module level wakeup events Govindraj.R
2012-04-24 16:07 ` Tony Lindgren
2012-04-24 14:09 ` [PATCH v3 2/2] ARM: omap3: pm: Remove uart module level wakeup configurations Govindraj.R
2012-04-25 7:17 ` [PATCH 1/2 v4] ARM: OMAP2+: omap_hwmod: Add api to enable/disable module level wakeup events Govindraj.R
2012-05-07 18:12 ` Kevin Hilman
2012-06-01 9:29 ` Menon, Nishanth
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=1335276552-24340-1-git-send-email-govindraj.raja@ti.com \
--to=govindraj.raja@ti.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;
as well as URLs for NNTP newsgroup(s).