Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Maxime Petazzoni <mpetazzoni@mvista.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Premi, Sanjeev" <premi@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: VDD1 voltage after resume from idle
Date: Fri, 20 Nov 2009 19:31:42 +0100	[thread overview]
Message-ID: <20091120183142.GD2354@mvista.com> (raw)
In-Reply-To: <87my2h3v9t.fsf@deeprootsystems.com>

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

* Kevin Hilman <khilman@deeprootsystems.com> [2009-11-20 10:29:02]:

> FWIW, the vdd*_opp sysfs hooks were for initial debug/dev and should
> be considered experimental (a.k.a broken.) They will disappear from
> the PM branch shortly.
> 
> CPUfreq should be the only interface used for DVFS.

Ah, well then I guess that fixes my problem. So, was I right on saying
that CPUfreq is "taking control" of the OPP values on wake up? (just
trying to make sure I understand how this works correctly).

Thanks for the info,
- Maxime
-- 
Maxime Petazzoni
Linux kernel & software dev
MontaVista Software, Inc

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-11-20 18:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 15:47 VDD1 voltage after resume from idle Premi, Sanjeev
2009-11-20 15:48 ` Menon, Nishanth
2009-11-20 15:54   ` Premi, Sanjeev
2009-11-20 15:59     ` Menon, Nishanth
2009-11-20 16:08       ` Premi, Sanjeev
2009-11-20 16:29 ` Maxime Petazzoni
2009-11-20 18:15   ` Premi, Sanjeev
2009-11-20 19:34     ` Premi, Sanjeev
2009-11-23 13:37       ` Premi, Sanjeev
2009-11-20 18:29   ` Kevin Hilman
2009-11-20 18:31     ` Maxime Petazzoni [this message]
2009-11-20 18:55     ` Jean Pihet
2009-11-20 19:11       ` Kevin Hilman
2009-11-20 19:19         ` Jean Pihet

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=20091120183142.GD2354@mvista.com \
    --to=mpetazzoni@mvista.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox