From: Kalle Jokiniemi <kalle.jokiniemi@digia.com>
To: khilman@deeprootsystems.com
Cc: linux-omap@vger.kernel.org, rnayak@ti.com,
jouni.hogander@nokia.com,
Kalle Jokiniemi <kalle.jokiniemi@digia.com>
Subject: [PATCH 1/3] OMAP:PM: Fix non-cpu idle builds using omap3_pm_init_cpuidle
Date: Thu, 29 Oct 2009 10:30:18 +0200 [thread overview]
Message-ID: <1256805020-7402-2-git-send-email-kalle.jokiniemi@digia.com> (raw)
In-Reply-To: <1256805020-7402-1-git-send-email-kalle.jokiniemi@digia.com>
Building without CONFIG_CPU_IDLE causes build to fail if
cpu idle parameters are tried to pass using
omap3_pm_init_cpuidle function.
Fixed by defining a dummy function for non-cpu idle
builds.
Signed-off-by: Kalle Jokiniemi <kalle.jokiniemi@digia.com>
---
arch/arm/mach-omap2/pm.h | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/pm.h b/arch/arm/mach-omap2/pm.h
index b576424..b9421e8 100644
--- a/arch/arm/mach-omap2/pm.h
+++ b/arch/arm/mach-omap2/pm.h
@@ -49,7 +49,14 @@ struct cpuidle_params {
};
extern void omap3_pm_init_vc(struct prm_setup_vc *setup_vc);
+#ifdef CONFIG_CPU_IDLE
extern void omap3_pm_init_cpuidle(struct cpuidle_params *cpuidle_board_params);
+#else
+static inline void omap3_pm_init_cpuidle(
+ struct cpuidle_params *cpuidle_board_params)
+{
+}
+#endif
extern int resource_set_opp_level(int res, u32 target_level, int flags);
extern int resource_access_opp_lock(int res, int delta);
--
1.5.4.3
next prev parent reply other threads:[~2009-10-29 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 8:30 [PATCH 0/3] Update CPU idle parameter passing Kalle Jokiniemi
2009-10-29 8:30 ` Kalle Jokiniemi [this message]
2009-10-29 8:30 ` [PATCH 2/3] OMAP3: Add valid field into C-state " Kalle Jokiniemi
2009-10-29 8:30 ` [PATCH 3/3] OMAP: RX-51: Pass cpu idle parameters Kalle Jokiniemi
2009-11-12 0:28 ` [PATCH 0/3] Update CPU idle parameter passing 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=1256805020-7402-2-git-send-email-kalle.jokiniemi@digia.com \
--to=kalle.jokiniemi@digia.com \
--cc=jouni.hogander@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@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 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.