linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:19:49 -0700	[thread overview]
Message-ID: <87zk7h5096.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.
>

BTW, after boot, can you run the shell snippet below.  This should run
the board through MPU DVFS for all the available OPPs:

Thanks,

Kevin


cd /sys/devices/system/cpu/cpu0/cpufreq
cat scaling_available_frequencies
cat scaling_cur_freq
echo userspace > scaling_governor

mpu_reg=regulator.3
for freq in `cat scaling_available_frequencies`; do
  echo ${freq} > scaling_setspeed
  echo -n "current freq: "
  cat scaling_cur_freq
  echo -n "current voltage: "
  cat /sys/class/regulator/${mpu_reg}/microvolts
  sleep 2
done

  parent reply	other threads:[~2012-07-02 21:19 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
2012-07-02 21:19 ` Kevin Hilman [this message]
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=87zk7h5096.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).