linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: Nishanth Menon <nm@ti.com>,
	Eduardo Valentin <eduardo.valentin@nokia.com>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	Paul Walmsley <paul@pwsan.com>, Rajendra Nayak <rnayak@ti.com>,
	Sanjeev Premi <premi@ti.com>, Thara Gopinath <thara@ti.com>,
	Tony Lindgren <tony@atomide.com>
Subject: [PM-OPP][PATCH 2/2] omap3: opp: make independent of cpufreq
Date: Tue, 10 Aug 2010 21:16:58 -0500	[thread overview]
Message-ID: <1281493018-29294-3-git-send-email-nm@ti.com> (raw)
In-Reply-To: <1281493018-29294-1-git-send-email-nm@ti.com>

Make opp3xx data which is registered with the opp layer
dependent purely on CONFIG_PM as opp layer and pm.c users
are CONFIG_PM dependent not cpufreq dependent.
so we rename the data definition to opp3xxx_data.c (inline with what
we have for omap2), also move the build definition to be under
the existing CONFIG_PM build instead of CPUFREQ.

Cc: Eduardo Valentin <eduardo.valentin@nokia.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Paul Walmsley <paul@pwsan.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Sanjeev Premi <premi@ti.com>
Cc: Thara Gopinath <thara@ti.com>
Cc: Tony Lindgren <tony@atomide.com>

Signed-off-by: Nishanth Menon <nm@ti.com>
---
Note:
This takes care of the discussion on opp file renaming and making
it independent of cpufreq, unless I missed something else

 arch/arm/mach-omap2/Makefile                       |    5 +----
 .../mach-omap2/{cpufreq34xx.c => opp3xxx_data.c}   |    0
 2 files changed, 1 insertions(+), 4 deletions(-)
 rename arch/arm/mach-omap2/{cpufreq34xx.c => opp3xxx_data.c} (100%)

diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
index 0b188fa..43d7372 100644
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
@@ -58,11 +58,8 @@ obj-$(CONFIG_OMAP_SMARTREFLEX_CLASS3)	+= smartreflex-class3.o
 AFLAGS_sleep24xx.o			:=-Wa,-march=armv6
 AFLAGS_sleep34xx.o			:=-Wa,-march=armv7-a
 
-endif
+obj-$(CONFIG_ARCH_OMAP3)		+= opp3xxx_data.o
 
-# CPU Frequency
-ifeq ($(CONFIG_CPU_FREQ),y)
-obj-$(CONFIG_ARCH_OMAP3)		+= cpufreq34xx.o
 endif
 
 # PRCM
diff --git a/arch/arm/mach-omap2/cpufreq34xx.c b/arch/arm/mach-omap2/opp3xxx_data.c
similarity index 100%
rename from arch/arm/mach-omap2/cpufreq34xx.c
rename to arch/arm/mach-omap2/opp3xxx_data.c
-- 
1.6.3.3


  parent reply	other threads:[~2010-08-11  2:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11  2:16 [PM-OPP][PATCH 0/2] OMAP: pm: opp: few additional cleanups Nishanth Menon
2010-08-11  2:16 ` [PM-OPP][PATCH 1/2] omap: pm: opp: remove opp_id Nishanth Menon
2010-08-11  2:16 ` Nishanth Menon [this message]
2010-08-11  9:12   ` [PM-OPP][PATCH 2/2] omap3: opp: make independent of cpufreq Gopinath, Thara
2010-08-11 10:43     ` Nishanth Menon
2010-08-11 11:23       ` Gopinath, Thara
2010-08-11 11:38         ` Nishanth Menon
2010-08-12 14:20           ` Gopinath, Thara
2010-08-12 14:34             ` Kevin Hilman
2010-08-12 15:27               ` Nishanth Menon

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=1281493018-29294-3-git-send-email-nm@ti.com \
    --to=nm@ti.com \
    --cc=eduardo.valentin@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=premi@ti.com \
    --cc=rnayak@ti.com \
    --cc=thara@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 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).