From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Swetland Subject: Re: [PATCH] omapfb vsync support Date: Mon, 27 Feb 2006 14:30:19 -0800 Message-ID: <20060227223019.GA29436@localhost.localdomain> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: "Woodruff, Richard" Cc: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org ["Woodruff, Richard" ] > 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