From: Rajendra Nayak <rnayak@ti.com>
To: linux-omap@vger.kernel.org
Cc: Rajendra Nayak <rnayak@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: [PATCH 1/5] OMAP4: runtime: Enable PM runtime core for OMAP4
Date: Mon, 9 Aug 2010 20:06:22 +0530 [thread overview]
Message-ID: <1281364586-26323-1-git-send-email-rnayak@ti.com> (raw)
The PM runtime core functions are implemented in pm_bus.c
which needs to be compiled for CONFIG_ARCH_OMAP4 for
runtime api's to work.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
---
arch/arm/mach-omap2/Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
index 800b430..18db759 100644
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
@@ -50,7 +50,7 @@ ifeq ($(CONFIG_PM),y)
obj-$(CONFIG_ARCH_OMAP2) += pm24xx.o
obj-$(CONFIG_ARCH_OMAP2) += sleep24xx.o
obj-$(CONFIG_ARCH_OMAP3) += pm34xx.o sleep34xx.o cpuidle34xx.o pm_bus.o
-obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o
+obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o pm_bus.o
obj-$(CONFIG_PM_DEBUG) += pm-debug.o
AFLAGS_sleep24xx.o :=-Wa,-march=armv6
--
1.5.4.7
next reply other threads:[~2010-08-09 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 14:36 Rajendra Nayak [this message]
2010-08-09 14:36 ` [PATCH 2/5] OMAP2xxx: hwmod: add I2C hwmods for OMAP2420, 2430 Rajendra Nayak
2010-08-09 14:36 ` [PATCH 3/5] OMAP3: hwmod: add I2C hwmods for OMAP3430 Rajendra Nayak
2010-08-09 14:36 ` [PATCH 4/5] OMAP: I2C: split device registration; convert OMAP2+ to omap_device Rajendra Nayak
2010-08-09 14:36 ` [PATCH 5/5] OMAP: I2C: Convert i2c driver to use PM runtime api's Rajendra Nayak
2010-08-23 22:23 ` Kevin Hilman
2010-08-25 8:43 ` Nayak, Rajendra
2010-08-23 22:18 ` [PATCH 2/5] OMAP2xxx: hwmod: add I2C hwmods for OMAP2420, 2430 Kevin Hilman
2010-08-25 8:42 ` Nayak, Rajendra
2010-08-23 22:16 ` [PATCH 1/5] OMAP4: runtime: Enable PM runtime core for OMAP4 Kevin Hilman
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=1281364586-26323-1-git-send-email-rnayak@ti.com \
--to=rnayak@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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).