From: Vaibhav Hiremath <[EMAIL PROTECTED]>

Fixed Community review comments:

s/g_input:
    Removed input/output related ioctl, and made
    use of s/g_routing ioctl. Added entry for the
    same to the v4l2-int framework.

s/g_input:
    Since from decoder point of view we really don't
    care about output, and anyway we can tie this
    feature with s/g_routing. So removed s/g_output
    ioctl.
    This was added for completeness in the previous patch.

Signed-off-by: Brijesh Jadav <[EMAIL PROTECTED]>
Signed-off-by: Hardik Shah <[EMAIL PROTECTED]>
Signed-off-by: Manjunath Hadli <[EMAIL PROTECTED]>
Signed-off-by: R Sivaraj <[EMAIL PROTECTED]>
Signed-off-by: Vaibhav Hiremath <[EMAIL PROTECTED]>
Signed-off-by: Karicheri Muralidharan <[EMAIL PROTECTED]>
---
 include/media/v4l2-int-device.h |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
 mode change 100644 => 100755 include/media/v4l2-int-device.h

diff --git a/include/media/v4l2-int-device.h b/include/media/v4l2-int-device.h
old mode 100644
new mode 100755
index 9c2df41..5e3e193
--- a/include/media/v4l2-int-device.h
+++ b/include/media/v4l2-int-device.h
@@ -183,6 +183,10 @@ enum v4l2_int_ioctl_num {
        vidioc_int_s_crop_num,
        vidioc_int_g_parm_num,
        vidioc_int_s_parm_num,
+       vidioc_int_querystd_num,
+       vidioc_int_s_std_num,
+       vidioc_int_g_video_routing_num,
+       vidioc_int_s_video_routing_num,

        /*
         *
@@ -284,6 +288,10 @@ V4L2_INT_WRAPPER_1(g_crop, struct v4l2_crop, *);
 V4L2_INT_WRAPPER_1(s_crop, struct v4l2_crop, *);
 V4L2_INT_WRAPPER_1(g_parm, struct v4l2_streamparm, *);
 V4L2_INT_WRAPPER_1(s_parm, struct v4l2_streamparm, *);
+V4L2_INT_WRAPPER_1(querystd, v4l2_std_id, *);
+V4L2_INT_WRAPPER_1(s_std, v4l2_std_id, *);
+V4L2_INT_WRAPPER_1(g_video_routing, int, *);
+V4L2_INT_WRAPPER_1(s_video_routing, int, );

 V4L2_INT_WRAPPER_0(dev_init);
 V4L2_INT_WRAPPER_0(dev_exit);
--
1.5.6

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to