linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: [PATCH RFC v6 07/12] v4l: add device capability flag for SDR receiver
Date: Wed, 15 Jan 2014 19:25:28 +0200	[thread overview]
Message-ID: <52D6C488.5090207@iki.fi> (raw)
In-Reply-To: <52D49691.4000405@iki.fi>

On 14.01.2014 03:44, Antti Palosaari wrote:
> On 05.01.2014 14:13, Hans Verkuil wrote:
>> On 12/29/2013 05:03 AM, Antti Palosaari wrote:
>>> VIDIOC_QUERYCAP IOCTL is used to query device capabilities. Add new
>>> capability flag to inform given device supports SDR capture.
>>>
>>> Cc: Hans Verkuil <hverkuil@xs4all.nl>
>>> Signed-off-by: Antti Palosaari <crope@iki.fi>
>>> Acked-by: Hans Verkuil <hverkuil@xs4all.nl>
>>> ---
>>>   include/uapi/linux/videodev2.h | 2 ++
>>>   1 file changed, 2 insertions(+)
>>>
>>> diff --git a/include/uapi/linux/videodev2.h
>>> b/include/uapi/linux/videodev2.h
>>> index c50e449..f596b7b 100644
>>> --- a/include/uapi/linux/videodev2.h
>>> +++ b/include/uapi/linux/videodev2.h
>>> @@ -267,6 +267,8 @@ struct v4l2_capability {
>>>   #define V4L2_CAP_RADIO            0x00040000  /* is a radio device */
>>>   #define V4L2_CAP_MODULATOR        0x00080000  /* has a modulator */
>>>
>>> +#define V4L2_CAP_SDR_CAPTURE        0x00100000  /* Is a SDR capture
>>> device */
>>> +
>>>   #define V4L2_CAP_READWRITE              0x01000000  /* read/write
>>> systemcalls */
>>>   #define V4L2_CAP_ASYNCIO                0x02000000  /* async I/O */
>>>   #define V4L2_CAP_STREAMING              0x04000000  /* streaming
>>> I/O ioctls */
>>>
>>
>> This new capability needs to be documented in DocBook as well
>> (vidioc-querycap.xml).
>
> It is already.

There is following related flags:

V4L2_CAP_TUNER
V4L2_CAP_RADIO
V4L2_CAP_MODULATOR
V4L2_CAP_SDR_CAPTURE

V4L2_CAP_TUNER flag is overlapping with all these and is redundant at 
least currently. Lets take a example as a radio device. There is 
V4L2_CAP_RADIO flag to say it is radio and then there is flag 
V4L2_CAP_TUNER which means signal is coming from antenna? So there could 
be radio device without V4L2_CAP_TUNER flag, for example radio over IP, 
right?

Due to that I started thinking relation of V4L2_CAP_SDR_CAPTURE and 
V4L2_CAP_TUNER and V4L2_CAP_RADIO flags. ADC is pretty much mandatory
element of SDR receiver (and DAC SDR transmitter). Whilst ADC is 
mandatory, RF tuner is not. So should I map V4L2_CAP_TUNER to indicate 
there is RF tuner?

regards
Antti

-- 
http://palosaari.fi/

  reply	other threads:[~2014-01-15 17:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-29  4:03 [PATCH RFC v6 00/12] SDR API with documentation Antti Palosaari
2013-12-29  4:03 ` [PATCH RFC v6 01/12] v4l: add device type for Software Defined Radio Antti Palosaari
2013-12-29  4:03 ` [PATCH RFC v6 02/12] v4l: add new tuner types for SDR Antti Palosaari
2013-12-29  4:03 ` [PATCH RFC v6 03/12] v4l: 1 Hz resolution flag for tuners Antti Palosaari
2013-12-29  4:03 ` [PATCH RFC v6 04/12] v4l: add stream format for SDR receiver Antti Palosaari
2013-12-29  4:03 ` [PATCH RFC v6 05/12] v4l: define own IOCTL ops for SDR FMT Antti Palosaari
2013-12-29  4:03 ` [PATCH RFC v6 06/12] v4l: enable some IOCTLs for SDR receiver Antti Palosaari
2013-12-29  4:03 ` [PATCH RFC v6 07/12] v4l: add device capability flag " Antti Palosaari
2014-01-05 12:13   ` Hans Verkuil
2014-01-14  1:44     ` Antti Palosaari
2014-01-15 17:25       ` Antti Palosaari [this message]
2014-01-15 18:18         ` Hans Verkuil
2013-12-29  4:04 ` [PATCH RFC v6 08/12] v4l: do not allow modulator ioctls for non-radio devices Antti Palosaari
2013-12-29  4:04 ` [PATCH RFC v6 09/12] DocBook: fix wait.c location Antti Palosaari
2013-12-29  4:04 ` [PATCH RFC v6 10/12] DocBook: document 1 Hz flag Antti Palosaari
2014-01-05 12:04   ` Hans Verkuil
2013-12-29  4:04 ` [PATCH RFC v6 11/12] DocBook: Software Defined Radio Interface Antti Palosaari
2014-01-05 12:11   ` Hans Verkuil
2013-12-29  4:04 ` [PATCH RFC v6 12/12] v4l2-framework.txt: add SDR device type Antti Palosaari
2014-01-05 12:15   ` 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=52D6C488.5090207@iki.fi \
    --to=crope@iki.fi \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    /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 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).