From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Cc: Thara Gopinath <thara@ti.com>
Subject: [PATCH 4/4] OMAP: Remove dependency of generic opp layer on cpufreq.
Date: Tue, 10 Aug 2010 17:09:17 -0700 [thread overview]
Message-ID: <1281485357-20791-5-git-send-email-khilman@deeprootsystems.com> (raw)
In-Reply-To: <1281485357-20791-1-git-send-email-khilman@deeprootsystems.com>
From: Thara Gopinath <thara@ti.com>
This patch removes the dependency of the opp layer on cpufreq layer.
OPP layer is now enabled to compile and exist in the system
irrespective of whether cpu freq layer is enabled or not.
[NM Note:
Original Patch: https://patchwork.kernel.org/patch/111664/
Still pending: http://marc.info/?l=linux-omap&m=127530955314582&w=2
To be squashed to patch 1
]
Signed-off-by: Thara Gopinath <thara@ti.com>
---
arch/arm/plat-omap/Makefile | 4 ++--
arch/arm/plat-omap/include/plat/opp.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/plat-omap/Makefile b/arch/arm/plat-omap/Makefile
index faf831d..852fa33 100644
--- a/arch/arm/plat-omap/Makefile
+++ b/arch/arm/plat-omap/Makefile
@@ -13,7 +13,7 @@ obj- :=
obj-$(CONFIG_ARCH_OMAP16XX) += ocpi.o
# OPP support in (OMAP3+ only at the moment)
-ifdef CONFIG_CPU_FREQ
+ifdef CONFIG_PM
obj-$(CONFIG_ARCH_OMAP3) += opp.o
obj-$(CONFIG_TWL4030_CORE) += opp_twl_tps.o
endif
@@ -37,4 +37,4 @@ obj-y += $(i2c-omap-m) $(i2c-omap-y)
# OMAP mailbox framework
obj-$(CONFIG_OMAP_MBOX_FWK) += mailbox.o
-obj-$(CONFIG_OMAP_PM_NOOP) += omap-pm-noop.o
\ No newline at end of file
+obj-$(CONFIG_OMAP_PM_NOOP) += omap-pm-noop.o
diff --git a/arch/arm/plat-omap/include/plat/opp.h b/arch/arm/plat-omap/include/plat/opp.h
index 403b69b..f9feb8d 100644
--- a/arch/arm/plat-omap/include/plat/opp.h
+++ b/arch/arm/plat-omap/include/plat/opp.h
@@ -61,7 +61,7 @@ struct omap_opp_def {
struct omap_opp;
-#ifdef CONFIG_CPU_FREQ
+#ifdef CONFIG_PM
unsigned long opp_get_voltage(const struct omap_opp *opp);
@@ -156,5 +156,5 @@ void opp_init_cpufreq_table(struct omap_opp *opps,
{
}
-#endif /* CONFIG_CPU_FREQ */
+#endif /* CONFIG_PM */
#endif /* __ASM_ARM_OMAP_OPP_H */
--
1.7.2.1
next prev parent reply other threads:[~2010-08-11 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 0:09 [PATCH 0/4] OMAP OPP layer Kevin Hilman
2010-08-11 0:09 ` [PATCH 1/4] OMAP: introduce OPP layer for device-specific OPPs Kevin Hilman
2010-08-11 0:09 ` [PATCH 2/4] omap: opp: twl/tps: Introduce TWL/TPS-specific code Kevin Hilman
2010-08-11 0:09 ` [PATCH 3/4] omap3: pm: remove OPP interfaces from OMAP PM layer Kevin Hilman
2010-08-11 0:09 ` Kevin Hilman [this message]
2010-08-11 0:17 ` [PATCH 0/4] OMAP OPP layer 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=1281485357-20791-5-git-send-email-khilman@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=thara@ti.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).