All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	Tero Kristo <tero.kristo@nokia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Vishwanath BS <vishwanath.bs@ti.com>
Subject: Re: VDD2 OPP and DSS
Date: Wed, 2 Mar 2011 09:18:20 +0200	[thread overview]
Message-ID: <20110302091820.0ffd5c5e.jhnikula@gmail.com> (raw)
In-Reply-To: <1299048012.2226.10.camel@deskari>

On Wed, 2 Mar 2011 08:40:12 +0200
Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:

> Hi Paul and Tero,
> 
> Some months ago there were discussions in Nokia about the problem with
> VDD2 OPP and DSS fck. The problem was (if I recall right) that the
> lowest VDD2 OPP cannot be used if DSS fck is over some certain limit (it
> was around 100MHz). If I understood correctly, this was also discussed
> with Paul.
> 
> Do you remember this (and did I remember it right =)? What is the status
> of this?
> 
At least lower OPP breaks DSS on N900 and Beagle if display is on while
entering into lower OPP.

This made me thinking that should initial round of
"[PATCH 10/13] OMAP3: Add voltage dependency table for VDD1."
use only OMAP3430_VDD_CORE_OPP3_UV for core voltage until there's some
dynamic/DSS voltage domain support in DSS?

http://marc.info/?l=linux-omap&m=129889365901937&w=2

That way, I believe, the DVFS has shorter path to mainline and makes
easier to add driver specific support & hooks. DVFS is not only power
savings but users are interesting about additional performance too.

https://bugs.meego.com/show_bug.cgi?id=13833

-- 
Jarkko

      reply	other threads:[~2011-03-02  7:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02  6:40 VDD2 OPP and DSS Tomi Valkeinen
2011-03-02  7:18 ` Jarkko Nikula [this message]

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=20110302091820.0ffd5c5e.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tero.kristo@nokia.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=vishwanath.bs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.