[RFC] Adding new ioctl for transparency color keying

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
OMAP class of device supports transparency color keying.  Color keying can be source color keying or destination color keying.

OMAP3 has three pipelines one graphics plane and two video planes.  Any of these pipelines can go to either the TV or LCD.  

The destination transparency color key value defines the encoded pixels in the graphics layer to become transparent and display the underlying video pixels. While the source transparency key value defines the encoded pixels in the video layer to become transparent and display the underlying graphics pixels.  This color keying works only if the video and graphics planes are on the same output like TV or LCD and images of both the pipelines overlapped.

I propose to have the one ioctl to set the encoded pixel value and type of color keying source and destination.  Also we should have the CID to enable/disable the color keying functionality.

Please let us know your opinions/comments.



Thanks and Regards,
Hardik Shah
 

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux