All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <snjw23@gmail.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	linux-media@vger.kernel.org, t.stanislaws@samsung.com
Subject: Re: [RFC] V4L: Rename V4L2_SEL_TGT_*_ACTIVE to V4L2_SEL_TGT_*_ACTUAL
Date: Sat, 05 May 2012 16:02:41 +0200	[thread overview]
Message-ID: <4FA53301.5030707@gmail.com> (raw)
In-Reply-To: <4FA52803.3040206@iki.fi>

Hi Sakari,

On 05/05/2012 03:15 PM, Sakari Ailus wrote:
> Sylwester Nawrocki wrote:
>> After introduction of the selection API on subdevs we have following sets
>> of selection targets:
>>
>> /dev/v4l-subdev? | /dev/video?
>> -------------------------------------------------------------------------
>> V4L2_SUBDEV_SEL_TGT_CROP_ACTUAL | V4L2_SEL_TGT_CROP_ACTIVE
>> V4L2_SUBDEV_SEL_TGT_CROP_BOUNDS | V4L2_SEL_TGT_CROP_BOUNDS
>> | V4L2_SEL_TGT_CROP_DEFAULT
>> | V4L2_SEL_TGT_CROP_PADDED
>> V4L2_SUBDEV_SEL_TGT_COMPOSE_ACTUAL | V4L2_SEL_TGT_COMPOSE_ACTIVE
>> V4L2_SUBDEV_SEL_TGT_COMPOSE_BOUNDS | V4L2_SEL_TGT_COMPOSE_BOUNDS
>> | V4L2_SEL_TGT_COMPOSE_DEFAULT
>> | V4L2_SEL_TGT_COMPOSE_PADDED
>>
>> Although not exactly the same, the meaning of V4L2_SEL_TGT_*_ACTIVE
>> and V4L2_SUBDEV_SEL_TGT_*_ACTUAL selection targets is logically the
>> same. Different names add to confusion where both APIs are used in
>> a single driver or an application.
>> Then, rename the V4l2_SEL_TGT_[CROP/COMPOSE]_ACTIVE to
>> V4l2_SEL_TGT_[CROP/COMPOSE]_ACTUAL to avoid the API inconsistencies.
>> The selections API is experimental, so no any compatibility layer
>> is added. The ABI remains unchanged.
> 
> I'm definitely for keeping the two sets of target as uniform as possible.
> 
> I have one question, though: how about dropping the ACTIVE / ACTUAL 
> altogether? Then we'd have V4L2_SUBDEV_SEL_TGT_CROP and 
> V4L2_SUBDEV_SEL_TGT_CROP_BOUNDS etc. I feel that the ACTIVE or ACTUAL 
> doesn't really say anything there, and don't think it's an issue that a 
> target name is a part of another one.

Agreed. I really like the idea of dropping the rather meaningless
postfixes. I don't see an issue here with the subdev API, 'crop/compose' 
and 'crop/compose bounds' would mean exactly what it says. Only 
V4L2_SEL_TGT_COMPOSE_PADDED stands a bit out. I don't see any driver
really using it at the moment though and I recall Tomasz saying it wasn't 
best idea to add it in first place. So I believe V4L2_SEL_TGT_COMPOSE_PADDED
might get removed from the API in future.

I'm going to rework the patch, then let's see what's Tomasz's and others'
opinion.

--

Regards,
Sylwester

      reply	other threads:[~2012-05-05 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 12:34 [RFC] V4L: Rename V4L2_SEL_TGT_*_ACTIVE to V4L2_SEL_TGT_*_ACTUAL Sylwester Nawrocki
2012-05-05 13:15 ` Sakari Ailus
2012-05-05 14:02   ` Sylwester Nawrocki [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=4FA53301.5030707@gmail.com \
    --to=snjw23@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=sylvester.nawrocki@gmail.com \
    --cc=t.stanislaws@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 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.