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 this control in driver, what will happen? Whether this will affect the functionality of the video streaming? or not. Why do we have the standard v4l2 ctrl like this? Thanks for the inputs. On 30 March 2018 at 12:58, Hans Verkuil <hverk...@xs4all.nl> wrote: > 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 receives power from the source (e.g. HDMI > carries 5V on one of the pins)." > > Regards, > > Hans > >> >> -Thanks. >> >> >> On 30 March 2018 at 12:13, Hans Verkuil <hverk...@xs4all.nl> 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 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 standard >>>> ctrl. When we need to use these standard ctrls?? >>> >>> No. This control is for HDMI receivers, not for sensors. >>> >>> Regards, >>> >>> Hans >>> >>>> >>>> 2. In Sensor driver, the ctrls creation is anything depends on the >>>> bridge driver. >>>> Based on bridge driver, whether we need to create any ctrls in Sensor >>>> driver. >>>> >>>> This question belongs to design of the sensor driver. >>>> >>>> >>>> >>>> Thanks & Regards >>>> >>> >
