Hi all, I had a discussion with Tomasz a few days ago on the selection API and how the composition fits to the proposal I made some time ago. I understand that in V4L2 API the composition bounds rectangle, onto which the scaled images are composed, is static in size. This makes no sense for subdevs as far as I can see.
In composition use cases there are also more than one sink pad whereas otherwise there is just a single pad in a subdev. In all use cases more than one source pad likely isn't uncommon. The problem with multiple sink pads is that which one you're referring to when you're configuring the first processing step on the source. Without composition there are no issues. What I can think of is to create a special composition target which is not bound to any pad, but reflects the size of the rectangle on which streams may be composed from source pad. Cropping on source pad refers to the coordinates of the composition rectangle. Composition target on sink pad in the original proposal would be renamed as the scaling target. There would also be no composition on source pads as it does not make that much sense. To make configuration simple, accessing any unsupported rectangles should return EINVAL. So devices not supporting composition would work as proposed earlier: the compose rectangle would be omitted and the sink crop (if supported) would refer to either scaling or crop targets or even the sink format directly. <URL:http://www.retiisi.org.uk/v4l2/tmp/format2.eps> Alternatively I think we could as well drop composition support at this point as we have no drivers using it. We still need to plan ahead how it could be supported as the need likely arises at some point. As far as I see the current interface proposal is compatible with composition. Should we discuss this further on #v4l-meeting, I propose Tuesday 2012-01-31 15:00 Finnish time (13:00 GMT). Kind regards, -- Sakari Ailus e-mail: sakari.ai...@iki.fi jabber/XMPP/Gmail: sai...@retiisi.org.uk -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
