From: Todd Poynor <toddpoynor@google.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap:pm: Fix boot-time errors with debugfs disabled
Date: Thu, 12 May 2011 12:58:41 -0700 [thread overview]
Message-ID: <20110512195841.GA13651@google.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024CE66D34@dbde02.ent.ti.com>
On Fri, May 13, 2011 at 12:46:17AM +0530, Premi, Sanjeev wrote:
> > -----Original Message-----
> > From: Menon, Nishanth
...
> > Last I tried, with Vishwa's dvfs branch on panda without voltage
> > registrations, things could crash :( if I get some time I will try to
> > port Vishwa's series onto kevin's branch as well and test and provide
> > any patches necessary.
>
> [sp] I can try this on Panda. Will be able to get one tomorrow.
In case it helps, below is what I use for Panda.
---
ARM: OMAP2 voltage: Don't die if board does not register voltage params
This allows the DVFS patches to boot on boards not yet modified to
register voltage params.
Signed-off-by: Todd Poynor <toddpoynor@google.com>
---
arch/arm/mach-omap2/voltage.c | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/voltage.c b/arch/arm/mach-omap2/voltage.c
index dbc1cfe..8f23d95 100644
--- a/arch/arm/mach-omap2/voltage.c
+++ b/arch/arm/mach-omap2/voltage.c
@@ -617,6 +617,12 @@ static void __init omap4_vc_init(struct omap_vdd_info *vdd)
struct clk *sys_ck;
u32 sys_clk_speed;
+ if (!vdd->board_data) {
+ pr_warning("%s: No voltage board params registered for vdd_%s\n",
+ __func__, vdd->voltdm.name);
+ return;
+ }
+
sys_ck = clk_get(NULL, "sys_clkin_ck");
if (IS_ERR(sys_ck)) {
pr_warning("%s: Could not get the sys clk to calculate"
--
1.7.3.1
next prev parent reply other threads:[~2011-05-12 19:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 17:36 [PATCH] omap:pm: Fix boot-time errors with debugfs disabled Sanjeev Premi
2011-05-12 18:02 ` Menon, Nishanth
2011-05-12 19:16 ` Premi, Sanjeev
2011-05-12 19:58 ` Todd Poynor [this message]
2011-05-12 21:03 ` Nishanth Menon
2011-05-13 12:48 ` Premi, Sanjeev
2011-05-17 14:40 ` Premi, Sanjeev
2011-05-18 8:25 ` Menon, Nishanth
2011-05-18 9:00 ` Premi, Sanjeev
2011-05-18 9:06 ` Menon, Nishanth
2011-05-18 9:16 ` Premi, Sanjeev
2011-05-18 16:34 ` Kevin Hilman
2011-05-18 18:48 ` Menon, Nishanth
2011-05-19 10:30 ` Premi, Sanjeev
2011-05-19 13:58 ` Menon, Nishanth
2011-05-20 15:21 ` Premi, Sanjeev
2011-05-24 23:57 ` 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=20110512195841.GA13651@google.com \
--to=toddpoynor@google.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=premi@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.