"Joe Woodward" <j...@terrafix.co.uk> writes: > I have a GUMSTIX Overo AirSTORM module (AM3703-based). > > When booting the kernel the following features are listed: > OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk ) > > After booting I get the following (repeating every few seconds): > > [ 81.122558] voltdm_scale: No voltage scale API registered for vdd_mpu_iva > [ 81.130340] platform mpu.0: omap_target: unable to scale voltage up.
Do you have CPUfreq enabled? I suspect so. With CPUfreq enabled, this seems to be happening once on boot, even on platforms with an IVA (like my Overo FireSTORM). But I'm very curious how it is happening every few seconds on your platform. Do you have the CPUfreq ondemand governor running with an active load? The boot-time warning seems to be an init ordering problem. The CPUfreq driver (upon registration) seems to try to set the frequency (and voltage), and this is happening before the voltage layer is fully initialized. I'm looking into this one. Why it would continue to happen after boot though is a bit of a mystery. I'm looking into that now. > I have SmartReflex enabled, and the same defconfig used to work on 3.4. > CONFIG_OMAP_SMARTREFLEX=y > CONFIG_OMAP_SMARTREFLEX_CLASS3=y > > I'm assuming this is because of changes to twl-common.c to add the "IVA" > voltage > domain, but on the OMAP I have there is no IVA - hence the warnings? I don't think it's related to IVA. The voltage domain contains both the MPU and the IVA (if present), so that voltage domain will be present on all SoCs in this family. > Is there a known fix for this (disabling SmartReflex seems to make no > difference)? I don't think it's related to SmartReflex either. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
