[media] pwc: Add a bunch of pwc custom API to feature-removal-schedule.txt

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index b1c921c27519a0953591b6a64159e46856e7558d..8a988e5708bac75feead9e53731a6cb2fb83c5d6 100644 (file)
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -584,6 +584,41 @@ Who:       Laurent Pinchart <laurent.pinchart@ideasonboard.com>
 
 ----------------------------
 
+What:  Support for driver specific ioctls in the pwc driver (everything
+       defined in media/pwc-ioctl.h)
+When:  3.3
+Why:   This stems from the v4l1 era, with v4l2 everything can be done with
+       standardized v4l2 API calls
+Who:   Hans de Goede <hdegoede@redhat.com>
+
+----------------------------
+
+What:  Driver specific sysfs API in the pwc driver
+When:  3.3
+Why:   Setting pan/tilt should be done with v4l2 controls, like with other
+       cams. The button is available as a standard input device
+Who:   Hans de Goede <hdegoede@redhat.com>
+
+----------------------------
+
+What:  Driver specific use of pixfmt.priv in the pwc driver
+When:  3.3
+Why:   The .priv field never was intended for this, setting a framerate is
+       support using the standardized S_PARM ioctl
+Who:   Hans de Goede <hdegoede@redhat.com>
+
+----------------------------
+
+What:  Software emulation of arbritary resolutions in the pwc driver
+When:  3.3
+Why:   The pwc driver claims to support any resolution between 160x120
+       and 640x480, but emulates this by simply drawing a black border
+       around the image. Userspace can draw its own black border if it
+       really wants one.
+Who:   Hans de Goede <hdegoede@redhat.com>
+
+----------------------------
+
 What:  For VIDIOC_S_FREQUENCY the type field must match the device node's type.
        If not, return -EINVAL.
 When:  3.2