RE: [PATCH] omapfb vsync support

Woodruff, Richard
2006-02-27T22:24:27Z

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.

Regards,
Richard W.

> -----Original Message-----
> From: linux-omap-open-source-bounces@linux.omap.com
[mailto:linux-omap-
> open-source-bounces@linux.omap.com] On Behalf Of Brian Swetland
> Sent: Monday, February 27, 2006 3:59 PM
> To: linux-omap-open-source@linux.omap.com
> Subject: [PATCH] omapfb vsync support
>
>
> Here's a patch that provides the FBIO_WAITFORVSYNC ioctl
> (same one used by the ati and nvidia drivers) to the omapfb
> driver. We could use the omap-specific ioctl, but it seemed
> to make more sense to use an existing one. Opinions?
>
> Brian