From: Kevin Hilman <khilman@ti.com>
To: Joe Woodward <jw@terrafix.co.uk>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: 3.5-rc3: vdd_mpu_iva warnings
Date: Mon, 02 Jul 2012 14:18:31 -0700 [thread overview]
Message-ID: <8762a56evs.fsf@ti.com> (raw)
In-Reply-To: <WC20120618103957.6103F2@terrafix.co.uk> (Joe Woodward's message of "Mon, 18 Jun 2012 11:39:57 +0100")
"Joe Woodward" <jw@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
next prev parent reply other threads:[~2012-07-02 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 10:39 3.5-rc3: vdd_mpu_iva warnings Joe Woodward
2012-06-27 15:22 ` Joe Woodward
2012-07-02 21:18 ` Kevin Hilman [this message]
2012-07-02 21:19 ` Kevin Hilman
2012-07-03 8:37 ` 3.5-rc3: PM/DSS broken (was vdd_mpu_iva warnings) Joe Woodward
2012-07-03 8:59 ` Archit Taneja
2012-07-03 9:12 ` Joe Woodward
2012-07-03 10:59 ` Archit Taneja
2012-07-03 12:31 ` Jassi Brar
2012-07-03 13:52 ` Joe Woodward
2012-07-04 14:01 ` Kevin Hilman
2012-07-05 7:58 ` Joe Woodward
2012-07-04 6:28 ` Tomi Valkeinen
2012-07-04 10:38 ` Archit Taneja
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=8762a56evs.fsf@ti.com \
--to=khilman@ti.com \
--cc=jw@terrafix.co.uk \
--cc=linux-omap@vger.kernel.org \
/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).