public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	linux-media@vger.kernel.org,
	Ismael Luceno <ismael.luceno@corp.bluecherry.net>,
	Sakari Ailus <sakari.ailus@iki.fi>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Pete Eberlein <pete@sensoray.com>
Subject: Re: [RFC PATCH 0/5] Matrix and Motion Detection support
Date: Tue, 16 Jul 2013 16:45:06 +0200	[thread overview]
Message-ID: <51E55C72.1050604@samsung.com> (raw)
In-Reply-To: <201307080922.34481.hverkuil@xs4all.nl>

Hi Hans,

On 07/08/2013 09:22 AM, Hans Verkuil wrote:
> On Sun July 7 2013 23:50:30 Sylwester Nawrocki wrote:
>> On 06/28/2013 02:27 PM, Hans Verkuil wrote:
>>> This patch series adds support for matrices and motion detection and
>>> converts the solo6x10 driver to use these new APIs.
>>>
>>> See the RFCv2 for details on the motion detection API:
>>>
>>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg62085.html
>>>
>>> And this RFC for details on the matrix API (which superseeds the v4l2_md_blocks
>>> in the RFC above):
>>>
>>> http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/65195
>>>
>>> I have tested this with the solo card, both global motion detection and
>>> regional motion detection, and it works well.
>>>
>>> There is no documentation for the new APIs yet (other than the RFCs). I would
>>> like to know what others think of this proposal before I start work on the
>>> DocBook documentation.
>>
>> These 3 ioctls look pretty generic and will likely allow us to handle wide
>> range of functionalities, similarly to what the controls framework does 
>> today.
>>
>> What I don't like in the current trend of the V4L2 API development 
>> though is
>> that we have seemingly separate APIs for configuring integers, rectangles,
>> matrices, etc. And interactions between those APIs sometimes happen to be
>> not well defined.
>>
>> I'm not opposed to having this matrix API, but I would _much_ more like to
>> see it as a starting point of a more powerful API, that would allow to 
>> model
>> dependencies between parameters being configured and the objects more
>> explicitly and freely (e.g. case of the per buffer controls), that would
>> allow to pass a list of commands to the hardware for atomic 
>> re-configurations,
>> that would allow to create hardware configuration contexts, etc., etc.
>>
>> But it's all song of future, requires lots of effort, founding and takes
>> engineers with significant experience.
>>
>> As it likely won't happen soon I guess we can proceed with the matrix API
>> for now.
> 
> Do you attend the LPC in New Orleans? I would like to discuss this further,
> but it is easier to do so face-to-face with a whiteboard. Alternatively, we
> could set up a brainstorm session somewhere. This discussion keeps cropping
> up time and again, perhaps we should start to do something about it :-)

My apologies for the delay. I'm not planning to attend LPC, certainly
discussing this in person sounds like a good idea. I will be most likely
attending ELCE in Edinburg though, perhaps we could have some meeting
organized there, if there are other persons interested in that.

--
Regards,
Sylwester

  reply	other threads:[~2013-07-16 14:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 12:27 [RFC PATCH 0/5] Matrix and Motion Detection support Hans Verkuil
2013-06-28 12:27 ` [RFC PATCH 1/5] v4l2: add matrix support Hans Verkuil
2013-07-07 21:50   ` Sylwester Nawrocki
2013-07-08  7:15     ` Hans Verkuil
2013-07-09  9:18       ` Sylwester Nawrocki
2013-07-10 20:59   ` Sakari Ailus
2013-06-28 12:27 ` [RFC PATCH 2/5] v4l2-compat-ioctl32: add g/s_matrix support Hans Verkuil
2013-07-18  0:22   ` Laurent Pinchart
2013-07-18  8:20     ` Hans Verkuil
2013-06-28 12:27 ` [RFC PATCH 3/5] solo: implement the new matrix ioctls instead of the custom ones Hans Verkuil
2013-06-28 12:27 ` [RFC PATCH 4/5] v4l2: add a motion detection event Hans Verkuil
2013-07-18  0:14   ` Laurent Pinchart
2013-07-18  8:19     ` Hans Verkuil
2013-06-28 12:27 ` [RFC PATCH 5/5] solo6x10: implement motion detection events and controls Hans Verkuil
2013-07-07 21:50 ` [RFC PATCH 0/5] Matrix and Motion Detection support Sylwester Nawrocki
2013-07-08  7:22   ` Hans Verkuil
2013-07-16 14:45     ` Sylwester Nawrocki [this message]
2013-07-18  0:12   ` Laurent Pinchart
2013-07-18  8:22     ` 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=51E55C72.1050604@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=hverkuil@xs4all.nl \
    --cc=ismael.luceno@corp.bluecherry.net \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=pete@sensoray.com \
    --cc=sakari.ailus@iki.fi \
    --cc=sylvester.nawrocki@gmail.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