* Video Signal Type in V4L
@ 2013-04-25 20:45 Abhishek Bansal
2013-04-25 20:53 ` Devin Heitmueller
2013-04-25 20:59 ` Mauro Carvalho Chehab
0 siblings, 2 replies; 3+ messages in thread
From: Abhishek Bansal @ 2013-04-25 20:45 UTC (permalink / raw)
To: linux-media
Hi All,
Is there any way by which I can know Input signal type (in terms of
DVI/Composite/USB/SDI) and refresh rate from a V4L video capture device.
Any available V4L Structure/Flag from which I can deduce this information.
Please help !
Thank You
Abhishek Bansal
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Video Signal Type in V4L
2013-04-25 20:45 Video Signal Type in V4L Abhishek Bansal
@ 2013-04-25 20:53 ` Devin Heitmueller
2013-04-25 20:59 ` Mauro Carvalho Chehab
1 sibling, 0 replies; 3+ messages in thread
From: Devin Heitmueller @ 2013-04-25 20:53 UTC (permalink / raw)
To: Abhishek Bansal; +Cc: Linux Media Mailing List
> Is there any way by which I can know Input signal type (in terms of
> DVI/Composite/USB/SDI) and refresh rate from a V4L video capture device.
> Any available V4L Structure/Flag from which I can deduce this information.
> Please help !
The extent to which the data is available is the name field in the G_FMT call:
http://linuxtv.org/downloads/v4l-dvb-apis/vidioc-enuminput.html
For most devices, the driver developer names the individual inputs
"Composite", "S-Video", "Tuner", etc.
The only level of distinction other than the name is the type field,
which today is V4L2_INPUT_TYPE_TUNER for an RF tuner and
V4L2_INPUT_TYPE_CAMERA for everything else.
To my knowledge there aren't any current drivers in the main tree that
support DVI or SDI capture, so nobody has really cared to make the API
more flexible to extend the "type" field with other values (which
would both be easier to machine parse, localize, and be consistent
across boards).
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Video Signal Type in V4L
2013-04-25 20:45 Video Signal Type in V4L Abhishek Bansal
2013-04-25 20:53 ` Devin Heitmueller
@ 2013-04-25 20:59 ` Mauro Carvalho Chehab
1 sibling, 0 replies; 3+ messages in thread
From: Mauro Carvalho Chehab @ 2013-04-25 20:59 UTC (permalink / raw)
To: Abhishek Bansal; +Cc: linux-media
Em Fri, 26 Apr 2013 02:15:03 +0530
"Abhishek Bansal" <abhishek@vizexperts.com> escreveu:
> Hi All,
>
> Is there any way by which I can know Input signal type (in terms of
> DVI/Composite/USB/SDI)
As input "type", currently no. However, by looking at the video input 'name'
field, it is possible to know if it is a composite, S-video, ... input entry.
The input name is a string, and the naming convention depends on the driver.
see field 'name' at
http://linuxtv.org/downloads/v4l-dvb-apis/vidioc-enuminput.html
And this ioctl for retrieving it for the current input:
http://linuxtv.org/downloads/v4l-dvb-apis/vidioc-g-input.html
> and refresh rate from a V4L video capture device.
Yes, via VIDIOC_G_PARM. see timeperframe field there:
http://linuxtv.org/downloads/v4l-dvb-apis/vidioc-g-parm.html
Not all drivers implement it through.
> Any available V4L Structure/Flag from which I can deduce this information.
> Please help !
>
> Thank You
> Abhishek Bansal
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Cheers,
Mauro
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-04-25 20:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-25 20:45 Video Signal Type in V4L Abhishek Bansal
2013-04-25 20:53 ` Devin Heitmueller
2013-04-25 20:59 ` Mauro Carvalho Chehab
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).