public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Swetland <swetland@google.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] omapfb vsync support
Date: Mon, 27 Feb 2006 14:30:19 -0800	[thread overview]
Message-ID: <20060227223019.GA29436@localhost.localdomain> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A50481E3A8@dlee02.ent.ti.com>

["Woodruff, Richard" <r-woodruff2@ti.com>]
> How come there is no disable of the interrupt?
> 
> Seems like at ioctrl the caller needs to be tracked so when he does a
> close the interrupt can be disabled.
> 
> This will cause a VST enabled kernel to wake up for no good reason if
> there is no application requesting it anymore.  Someone pointed out this
> fact to me recently while doing power measurements.  If you have a low
> power screen saver mode this can mess up expected power savings.

Hmm.  I wonder if there's some happy medium between disabling the 
interrupt every time the ioctl returns and having to close and reopen
the driver when going into and returning from low power mode.

Brian

  reply	other threads:[~2006-02-27 22:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 22:24 [PATCH] omapfb vsync support Woodruff, Richard
2006-02-27 22:30 ` Brian Swetland [this message]
2006-02-27 23:27   ` Mathias Agopian
2006-02-28 10:47     ` Imre Deak
  -- strict thread matches above, loose matches on Subject: below --
2006-02-28 12:54 Woodruff, Richard
2006-02-27 23:43 Woodruff, Richard
2006-02-27 23:10 Woodruff, Richard
2006-02-27 21:59 Brian Swetland

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=20060227223019.GA29436@localhost.localdomain \
    --to=swetland@google.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=r-woodruff2@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