Hi Tero,
Thanks for the reply. I'll try this out. I don't think mpu_opps is
defined for my board_overo.c file. I guess I should look at the
board_sdp3430.c as an example for this?
Thanks and do let me know!
Best regards,
Elvis
On May 19, 2009, at 3:41 PM, Tero.Kristo@xxxxxxxxx wrote:
Hi Elvis,
I think I saw something similar last week, and it was caused by not
having CONFIG_OMAP_PM_SRF enabled. The actual culprit is the marked
line in sr_configure_vp():
vpconfig = PRM_VP1_CONFIG_ERROROFFSET |
PRM_VP1_CONFIG_ERRORGAIN |
PRM_VP1_CONFIG_TIMEOUTEN |
mpu_opps[resource_get_level("vdd1_opp")].vsel <<
OMAP3430_INITVOLTAGE_SHIFT;
SR2 has similar code a bit later.
You will also get a failure if mpu_opps[] and/or l3_opps[] is not
defined at all in your board files, this null pointer exception
would actually indicate a problem like that more likely.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
