On 03/04/18 08:32, asadpt iqroot wrote:
> Hi Hans,
>
> Thanks for the reply.
>
> In board, we have the HDMI connectors. Is it mandatory to use this ctrl
> V4L2_CID_DV_RX_POWER_PRESENT. Based on this v4l2 ctrl, what v4l2 framework
> will do? If I do not set any value to this ctrl, what will happen
Hi Hans,
Thanks for the reply.
In board, we have the HDMI connectors. Is it mandatory to use this ctrl
V4L2_CID_DV_RX_POWER_PRESENT. Based on this v4l2 ctrl, what v4l2 framework
will do? If I do not set any value to this ctrl, what will happen to
video streaming?
For example, if I did not add th
On 30/03/18 09:23, asadpt iqroot wrote:
> Hi Hans,
>
> Thanks for the reply.
>
> In HDMI receivers, when we need to use this control. What scenario?
https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/v4l/extended-controls.html#digital-video-control-reference
"Detects whether the receiver r
Hi Hans,
Thanks for the reply.
In HDMI receivers, when we need to use this control. What scenario?
-Thanks.
On 30 March 2018 at 12:13, Hans Verkuil wrote:
> On 30/03/18 08:16, asadpt iqroot wrote:
>> Hi All,
>>
>> In reference sensor drivers, they used the
>> V4L2_CID_DV_RX_POWER_PRESENT v4l2
On 30/03/18 08:16, asadpt iqroot wrote:
> Hi All,
>
> In reference sensor drivers, they used the
> V4L2_CID_DV_RX_POWER_PRESENT v4l2 ctrl.
> It is a standard ctrl and created using v4l2_ctrl_new_std().
>
> The doubts are:
>
> 1. Whether in our sensor driver, we need to create this Control Id or
Hi All,
In reference sensor drivers, they used the
V4L2_CID_DV_RX_POWER_PRESENT v4l2 ctrl.
It is a standard ctrl and created using v4l2_ctrl_new_std().
The doubts are:
1. Whether in our sensor driver, we need to create this Control Id or
not. How to take the decision on this. Since this is the s
