From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Varadarajan, Charulatha" <charu@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, b-cousson@ti.com,
tony@atomide.com, rnayak@ti.com, p-basak2@ti.com
Subject: Re: [PATCH] OMAP2: Add pm_bus.c file for OMAP2 architecture
Date: Mon, 13 Sep 2010 07:58:57 -0700 [thread overview]
Message-ID: <878w351yha.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1284367481-10508-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Mon, 13 Sep 2010 14:14:41 +0530")
"Varadarajan, Charulatha" <charu@ti.com> writes:
> This patch adds pm_bus.o for OMAP2 architecture which is required
> while using PM runtime APIs on OMAP2.
>
> This patch series is created on "origin/pm-core" and is
> tested on 2430 SDP board (with watchdog and GPIO patches
> using PM runtime APIs. These patches would be sent to
> LO mailing list soon).
>
> Signed-off-by: Charulatha V <charu@ti.com>
Thanks, will merge into runtime PM core before final version is posted.
Kevin
> ---
> 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 56133d4..a88b75a 100644
> --- a/arch/arm/mach-omap2/Makefile
> +++ b/arch/arm/mach-omap2/Makefile
> @@ -51,7 +51,7 @@ obj-$(CONFIG_ARCH_OMAP2) += sdrc2xxx.o
> # Power Management
> ifeq ($(CONFIG_PM),y)
> obj-$(CONFIG_ARCH_OMAP2) += pm24xx.o
> -obj-$(CONFIG_ARCH_OMAP2) += sleep24xx.o
> +obj-$(CONFIG_ARCH_OMAP2) += sleep24xx.o pm_bus.o
> obj-$(CONFIG_ARCH_OMAP3) += pm34xx.o sleep34xx.o cpuidle34xx.o pm_bus.o
> obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o pm_bus.o
> obj-$(CONFIG_PM_DEBUG) += pm-debug.o
prev parent reply other threads:[~2010-09-13 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 8:44 [PATCH] OMAP2: Add pm_bus.c file for OMAP2 architecture Varadarajan, Charulatha
2010-09-13 14:58 ` Kevin Hilman [this message]
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=878w351yha.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=charu@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--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 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.