On 12/03/14 12:06, Sakari Ailus wrote: > Hi Hans, > > On Tue, Dec 02, 2014 at 01:21:40PM +0100, Hans Verkuil wrote: >> From: Hans Verkuil <hans.verkuil@xxxxxxxxx> >> >> The crop and selection pad ops are duplicates. Replace all uses of get/set_crop >> by get/set_selection. This will make it possible to drop get/set_crop >> altogether. >> >> Signed-off-by: Hans Verkuil <hans.verkuil@xxxxxxxxx> >> Cc: Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx> >> Cc: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> >> Cc: Prabhakar Lad <prabhakar.csengg@xxxxxxxxx> >> Cc: Philipp Zabel <p.zabel@xxxxxxxxxxxxxx> > > For both: > > Acked-by: Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx> > > Another point I'd like to draw attention to are the reserved fields --- some > drivers appear to zero them whereas some pay no attention. Shouldn't we > check in the sub-device IOCTL handler that the user has zeroed them, or zero > them for the user? I think this has probably been discussed before on V4L2. > Both have their advantages, probably zeroing them in the framework would be > the best option. What do you think? If the framework can zero, then that's always better. Also note that valgrind understands the subdev ioctls, so that will be able to checks apps as well. I haven't really looked into this yet, but I'm happy to review patches :-) Regards, Hans -- 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
