From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: V4l2 Sensor driver and V4l2 ctrls
Date: Fri, 30 Mar 2018 03:12:08 -0400 [thread overview]
Message-ID: <32051.1522393928@turing-police.cc.vt.edu> (raw)
In-Reply-To: <16275853886.d54106f2524214.7152654289021633598@iqroottech.com>
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. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180330/5e9cee3b/attachment.sig>
next prev parent reply other threads:[~2018-03-30 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 6:08 V4l2 Sensor driver and V4l2 ctrls MUHAMMED ASAD P T
2018-03-30 7:12 ` valdis.kletnieks at vt.edu [this message]
2018-04-03 6:45 ` MUHAMMED ASAD P T
2018-03-30 6:16 asadpt iqroot
2018-03-30 6:43 ` Hans Verkuil
2018-03-30 7:23 ` asadpt iqroot
2018-03-30 7:28 ` Hans Verkuil
2018-04-03 6:32 ` asadpt iqroot
2018-04-03 7:25 ` Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32051.1522393928@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.