From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Abhishek Bansal" <abhishek@vizexperts.com>
Cc: <linux-media@vger.kernel.org>
Subject: Re: Video Signal Type in V4L
Date: Thu, 25 Apr 2013 17:59:54 -0300 [thread overview]
Message-ID: <20130425175954.71ecd0f1@redhat.com> (raw)
In-Reply-To: <001901ce41f5$c4da31f0$4e8e95d0$@vizexperts.com>
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
prev parent reply other threads:[~2013-04-25 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=20130425175954.71ecd0f1@redhat.com \
--to=mchehab@redhat.com \
--cc=abhishek@vizexperts.com \
--cc=linux-media@vger.kernel.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.