public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: [REVIEW PATCH 3/6] v4l: reorganize RF tuner control ID numbers
Date: Fri, 14 Feb 2014 16:36:41 +0200	[thread overview]
Message-ID: <52FE29F9.3000702@iki.fi> (raw)
In-Reply-To: <52FE263E.9010408@xs4all.nl>

On 14.02.2014 16:20, Hans Verkuil wrote:
> Hi Antti,
>
> On 02/10/2014 05:17 PM, Antti Palosaari wrote:
>> It appears that controls are ordered by ID number. Change order of
>> controls by reorganizing assigned IDs now as we can. It is not
>> reasonable possible after the API is released. Leave some spare
>> space between IDs too for future extensions.
>
> Am I missing something? I see no reason for this patch or for adding the
> spare space.

"It appears that controls are ordered by ID number"

I used app called v4l2ucp and at least it seems to organize those 
controls by ID. Is there some way to say application how those are 
organized?

regards
Antti


>
> Regards,
>
> 	Hans
>
>>
>> Cc: Hans Verkuil <hverkuil@xs4all.nl>
>> Signed-off-by: Antti Palosaari <crope@iki.fi>
>> ---
>>   include/uapi/linux/v4l2-controls.h | 16 ++++++++--------
>>   1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/include/uapi/linux/v4l2-controls.h b/include/uapi/linux/v4l2-controls.h
>> index 3cf68a6..cc488c3 100644
>> --- a/include/uapi/linux/v4l2-controls.h
>> +++ b/include/uapi/linux/v4l2-controls.h
>> @@ -899,13 +899,13 @@ enum v4l2_deemphasis {
>>   #define V4L2_CID_RF_TUNER_CLASS_BASE		(V4L2_CTRL_CLASS_RF_TUNER | 0x900)
>>   #define V4L2_CID_RF_TUNER_CLASS			(V4L2_CTRL_CLASS_RF_TUNER | 1)
>>
>> -#define V4L2_CID_LNA_GAIN_AUTO			(V4L2_CID_RF_TUNER_CLASS_BASE + 1)
>> -#define V4L2_CID_LNA_GAIN			(V4L2_CID_RF_TUNER_CLASS_BASE + 2)
>> -#define V4L2_CID_MIXER_GAIN_AUTO		(V4L2_CID_RF_TUNER_CLASS_BASE + 3)
>> -#define V4L2_CID_MIXER_GAIN			(V4L2_CID_RF_TUNER_CLASS_BASE + 4)
>> -#define V4L2_CID_IF_GAIN_AUTO			(V4L2_CID_RF_TUNER_CLASS_BASE + 5)
>> -#define V4L2_CID_IF_GAIN			(V4L2_CID_RF_TUNER_CLASS_BASE + 6)
>> -#define V4L2_CID_BANDWIDTH_AUTO			(V4L2_CID_RF_TUNER_CLASS_BASE + 7)
>> -#define V4L2_CID_BANDWIDTH			(V4L2_CID_RF_TUNER_CLASS_BASE + 8)
>> +#define V4L2_CID_BANDWIDTH_AUTO			(V4L2_CID_RF_TUNER_CLASS_BASE + 11)
>> +#define V4L2_CID_BANDWIDTH			(V4L2_CID_RF_TUNER_CLASS_BASE + 12)
>> +#define V4L2_CID_LNA_GAIN_AUTO			(V4L2_CID_RF_TUNER_CLASS_BASE + 41)
>> +#define V4L2_CID_LNA_GAIN			(V4L2_CID_RF_TUNER_CLASS_BASE + 42)
>> +#define V4L2_CID_MIXER_GAIN_AUTO		(V4L2_CID_RF_TUNER_CLASS_BASE + 51)
>> +#define V4L2_CID_MIXER_GAIN			(V4L2_CID_RF_TUNER_CLASS_BASE + 52)
>> +#define V4L2_CID_IF_GAIN_AUTO			(V4L2_CID_RF_TUNER_CLASS_BASE + 61)
>> +#define V4L2_CID_IF_GAIN			(V4L2_CID_RF_TUNER_CLASS_BASE + 62)
>>
>>   #endif
>>
>


-- 
http://palosaari.fi/

  reply	other threads:[~2014-02-14 14:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 16:17 [REVIEW PATCH 0/6] SDR API - V4L implement needed controls and formats Antti Palosaari
2014-02-10 16:17 ` [REVIEW PATCH 1/6] v4l: add RF tuner gain controls Antti Palosaari
2014-02-14 14:30   ` Hans Verkuil
2014-02-14 14:44     ` Antti Palosaari
2014-02-14 14:47       ` Hans Verkuil
2014-02-10 16:17 ` [REVIEW PATCH 2/6] v4l: add RF tuner channel bandwidth control Antti Palosaari
2014-02-14 14:31   ` Hans Verkuil
2014-02-10 16:17 ` [REVIEW PATCH 3/6] v4l: reorganize RF tuner control ID numbers Antti Palosaari
2014-02-14 14:20   ` Hans Verkuil
2014-02-14 14:36     ` Antti Palosaari [this message]
2014-02-14 14:44       ` Hans Verkuil
2014-02-10 16:17 ` [REVIEW PATCH 4/6] v4l: uapi: add SDR formats CU8 and CU16LE Antti Palosaari
2014-02-10 16:17 ` [REVIEW PATCH 5/6] v4l: add enum_freq_bands support to tuner sub-device Antti Palosaari
2014-02-10 16:17 ` [REVIEW PATCH 6/6] v4l: add control for RF tuner PLL lock flag Antti Palosaari

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=52FE29F9.3000702@iki.fi \
    --to=crope@iki.fi \
    --cc=hverkuil@xs4all.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox