public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: tomi.valkeinen@nokia.com
Cc: ext Mike Chan <mike@android.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] video: omap2: dss: RET on idle, enable/disable dss clocks 	only when needed.
Date: Tue, 22 Sep 2009 07:54:20 -0700	[thread overview]
Message-ID: <877hvrf2sj.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1253514408.4690.5.camel@tubuntu> (Tomi Valkeinen's message of "Mon\, 21 Sep 2009 09\:26\:48 +0300")

Tomi Valkeinen <tomi.valkeinen@nokia.com> writes:

> Hi,
>
> On Fri, 2009-09-18 at 19:33 +0200, ext Mike Chan wrote:
>> On Fri, Sep 18, 2009 at 1:27 AM, Tomi Valkeinen
>> <tomi.valkeinen@nokia.com> wrote:
>> > Hi,
>> >
>> > If you disable the clocks to allow RET, you also allow OFF mode. And
>> > resuming from OFF mode hasn't been implemented for DSI, if I recall
>> > right. And when I was testing it, it didn't seem to be trivial with the
>> > DSI PLL.
>> >
>> 
>> You can limiting the pwrdm next state to RET when being called from cpuidle.
>
> No, you _must_ limit it to RET. Otherwise the DSI will break down. So we
> can either keep the dsi code as it is now, or explicitely disable OFF
> mode and then apply your patch. But your patch alone won't work.

Or could add a hack to this patch so that 'enable_off_mode' doesn't
affect DSS_MOD until DSS has off-mode support.

> In the long run I think we anyway need to somehow dynamically manage the
> power state. I haven't measured it but I believe resuming from OFF will
> have a bit of a penalty, as (I think) DSI PLL etc. will have to
> reinitialized. But it would still be good to allow RET whenever
> possible, and OFF only after some period of inactivity.

This is the purpose of latency constraints.  These can be used when
the latency of going OFF will cause a problem.

Kevin

  reply	other threads:[~2009-09-22 14:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 23:36 [PATCH] video: omap2: dss: RET on idle, enable/disable dss clocks only when needed Mike Chan
2009-09-17 23:38 ` Mike Chan
2009-09-18  8:27 ` Tomi Valkeinen
2009-09-18 17:33   ` Mike Chan
2009-09-21  6:26     ` Tomi Valkeinen
2009-09-22 14:54       ` Kevin Hilman [this message]
2009-09-23  7:20         ` Tomi Valkeinen
2009-09-23 15:44           ` Kevin Hilman
2009-09-24 10:39             ` Tomi Valkeinen
2009-09-24 15:52               ` Kevin Hilman
2009-09-25  9:19                 ` Tomi Valkeinen
2009-09-30 18:31                   ` Kevin Hilman
2009-10-01 14:40                     ` Tomi Valkeinen
2009-10-01 16:19                       ` Kevin Hilman
2009-10-02  8:03                         ` Tomi Valkeinen
2009-10-02 14:27                           ` Kevin Hilman

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=877hvrf2sj.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike@android.com \
    --cc=tomi.valkeinen@nokia.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