V4l2 Sensor driver and V4l2 ctrls
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?? 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 - Asad IQ Root Technologies
On Fri, 30 Mar 2018 11:38:07 +0530, MUHAMMED ASAD P T said:
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().
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??
When you're doing the same thing as the reference drivers, use the standard control. If you're doing something strange and different from the reference drivers, ask yourself why you're doing it, and whether doing the same thing as the reference drivers wouldn't be a better idea. In this specific case, RX_POWER_PRESENT sounds like a pretty common thing to be able to sense. So if that's what you're doing, use that control. If your sensor can't detect RX_POWER_PRESENT, complain to your hardware design team. :)
Hi, Thanks for the reply. In board, HDMI connectors are there. If we did not add this ctrl in driver, what will happen to the functionality? If we did not add this ctrl, then whether this affect the video streaming functionality or not? What scenario, we need to add this ctrl? Thanks for the inputs. Thanks & Regards - Asad IQ Root Technologies ---- On Fri, 30 Mar 2018 12:42:08 +0530 <valdis.kletnieks@vt.edu> wrote ---- On Fri, 30 Mar 2018 11:38:07 +0530, MUHAMMED ASAD P T said: > 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(). > 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?? When you're doing the same thing as the reference drivers, use the standard control. If you're doing something strange and different from the reference drivers, ask yourself why you're doing it, and whether doing the same thing as the reference drivers wouldn't be a better idea. In this specific case, RX_POWER_PRESENT sounds like a pretty common thing to be able to sense. So if that's what you're doing, use that control. If your sensor can't detect RX_POWER_PRESENT, complain to your hardware design team. :)
participants (2)
-
MUHAMMED ASAD P T -
valdis.kletnieks＠vt.edu