Currently mem-to-mem devices are identified through V4L2_CAP_VIDEO_CAPTURE and V4L2_CAP_VIDEO_OUTPUT capabilities. This is not reliable and may lead to false identification of mem-to-mem devices as video capture or output devices, if an application doesn't check both flags. As a follow up to an RFC from Kamil http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg22363.html this changeset adds new capability flags for mem-to-mem devices: V4L2_CAP_VIDEO_M2M and V4L2_CAP_VIDEO_M2M_MPLANE. For backward compatibility with existing applications Capture and Output capability flags are not removed at the drivers. These are intended to be removed later after some transition period. However, in practice I wouldn't expect problems, as all current mem-to-mem drivers are now for embedded devices. So two kernel releases transition period might be an overkill here. Comments ? Regards, Sylwester Sylwester Nawrocki (2): V4L: Add capability flags for memory-to-memory devices Feature removal: Using capture and output capabilities for m2m devices Documentation/DocBook/media/v4l/compat.xml | 9 +++++++++ .../DocBook/media/v4l/vidioc-querycap.xml | 13 +++++++++++++ Documentation/feature-removal-schedule.txt | 14 ++++++++++++++ drivers/media/video/mem2mem_testdev.c | 4 +--- drivers/media/video/mx2_emmaprp.c | 10 +++++++--- drivers/media/video/s5p-fimc/fimc-m2m.c | 7 ++++++- drivers/media/video/s5p-g2d/g2d.c | 9 +++++++-- drivers/media/video/s5p-jpeg/jpeg-core.c | 10 +++++++--- drivers/media/video/s5p-mfc/s5p_mfc_dec.c | 10 ++++++++-- drivers/media/video/s5p-mfc/s5p_mfc_enc.c | 11 ++++++++--- include/linux/videodev2.h | 4 ++++ 11 files changed, 84 insertions(+), 17 deletions(-) -- 1.7.4.1 -- 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
