Sakari Ailus wrote: ... > On second thought, I think I'll combine them into a new anonymous struct > the field name of which I call "pad", unless that requires too intrusive > changes in other drivers. How about that? And the answer to that is "no". The smia++ driver does store the format, crop and compose values in arrays indexed by pad numbers which I think is a natural thing for the driver to do. In many functiona the driver uses internally it's trivial to choose the array either from driver's internal data structure (V4L2_SUBDEV_FORMAT_ACTIVE) or the file handle (V4L2_SUBDEV_FORMAT_TRY). Alternatively a named struct could be created for the same, but the drivers might not need all the fields at all, or choose to store them in a different form. -- Sakari Ailus sakari.ailus@xxxxxxxxxxxxxxxxxxxxxxxxxx -- 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
