Hi Hans,
The patch seems to cover most of the requirement. I find 2 gaps:
> +/* DV-class control IDs defined by V4L2 */
> +#define V4L2_CID_DV_CLASS_BASE (V4L2_CTRL_CLASS_DV | 0x900)
> +#define V4L2_CID_DV_CLASS (V4L2_CTRL_CLASS_DV | 1)
> +
> +#define
On Mon August 13 2012 13:48:28 Soby Mathew wrote:
> Hi Hans,
>The patch seems to cover most of the requirement. I find 2 gaps:
>
> > +/* DV-class control IDs defined by V4L2 */
> > +#define V4L2_CID_DV_CLASS_BASE (V4L2_CTRL_CLASS_DV | 0x900)
> > +#define V4L2_CID_DV_CLASS
On Mon August 13 2012 13:48:28 Soby Mathew wrote:
Hi Hans,
The patch seems to cover most of the requirement. I find 2 gaps:
+/* DV-class control IDs defined by V4L2 */
+#define V4L2_CID_DV_CLASS_BASE (V4L2_CTRL_CLASS_DV | 0x900)
+#define V4L2_CID_DV_CLASS
Hi Hans,
The patch seems to cover most of the requirement. I find 2 gaps:
+/* DV-class control IDs defined by V4L2 */
+#define V4L2_CID_DV_CLASS_BASE (V4L2_CTRL_CLASS_DV | 0x900)
+#define V4L2_CID_DV_CLASS (V4L2_CTRL_CLASS_DV | 1)
+
+#define
These new controls and two new ioctls make it possible to properly support
VGA, DVI-A/D/I, HDMI and DisplayPort connectors. All these controls and the
ioctls are all at the sub-device level. They are meant for V4L2 bridge/platform
drivers or to be accessed on embedded systems through
These new controls and two new ioctls make it possible to properly support
VGA, DVI-A/D/I, HDMI and DisplayPort connectors. All these controls and the
ioctls are all at the sub-device level. They are meant for V4L2 bridge/platform
drivers or to be accessed on embedded systems through
