Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit a1367f1b authored by Sylwester Nawrocki's avatar Sylwester Nawrocki Committed by Mauro Carvalho Chehab
Browse files

[media] Feature removal: using capture and output capabilities for m2m devices 



Identifying a memory-to-memory video device through an ORed output and
capture capability flags is not reliable. Schedule this for removal.

Signed-off-by: default avatarSylwester Nawrocki <s.nawrocki@samsung.com>
Signed-off-by: default avatarKyungmin Park <kyungmin.park@samsung.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
parent f0476a83

Documentation/feature-removal-schedule.txt

+14 −0
Original line number Diff line number Diff line
@@ -576,3 +576,17 @@ Why: The regular V4L2 selections and the subdev selection API originally 
	any instabilities in the user space interface. After few cycles these

	backward compatibility definitions will be removed.

Who:	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>



----------------------------



What:	Using V4L2_CAP_VIDEO_CAPTURE and V4L2_CAP_VIDEO_OUTPUT flags

	to indicate a V4L2 memory-to-memory device capability

When:	3.8

Why:	New drivers should use new V4L2_CAP_VIDEO_M2M capability flag

	to indicate a V4L2 video memory-to-memory (M2M) device and

	applications can now identify a M2M video device by checking

	for V4L2_CAP_VIDEO_M2M, with VIDIOC_QUERYCAP ioctl. Using ORed

	V4L2_CAP_VIDEO_CAPTURE and V4L2_CAP_VIDEO_OUTPUT flags for M2M

	devices is ambiguous and may lead, for example, to identifying

	a M2M device as a video	capture or output device.

Who:	Sylwester Nawrocki <s.nawrocki@samsung.com>