public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	"Ivan T. Ivanov" <iivanov@mm-sol.com>,
	Guru Raj <gururaj.nagendra@intel.com>,
	Cohen David Abraham <david.cohen@nokia.com>
Subject: [PATCH v4 0/7] V4L2 file handles and event interface
Date: Wed, 10 Feb 2010 16:57:41 +0200	[thread overview]
Message-ID: <4B72C965.7040204@maxwell.research.nokia.com> (raw)

Hi,

Here's the sixth version of the V4L2 file handle and event interface
patchset.

The first patch adds the V4L2 file handle support and the rest are for
V4L2 events.

The patchset has been tested with the OMAP 3 ISP driver. Patches for
OMAP 3 ISP are not part of this patchset but are available in Gitorious
(branch is called event):

	git://gitorious.org/omap3camera/mainline.git event

Some more comments from Hans. What has changed:

- Events are timestamped in v4l2_event_queue().
- No ioctl handler for vidioc_dqevent or vidioc_unsubscribe_event
anymore. The __video_do_ioctl() calls directly v4l2_event_dequeue() and
v4l2_event_unsubscribe().
- v4l2_event->navailable and v4l2_event->max_alloc (was max_events) are
now unsigned int instead of atomic_t. They are modified only when the
video_device->fh_lock is held.
- No longer possible to allocate any more events than the limit in
v4l2_event_alloc().

- Possibly something else I don't happen to remember just now.

Comments are welcome as always.

Cheers,

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com


             reply	other threads:[~2010-02-10 14:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 14:57 Sakari Ailus [this message]
2010-02-10 14:58 ` [PATCH v4 1/7] V4L: File handles Sakari Ailus
2010-02-10 14:58   ` [PATCH v4 2/7] V4L: Events: Add new ioctls for events Sakari Ailus
2010-02-10 14:58     ` [PATCH v4 3/7] V4L: Events: Add backend Sakari Ailus
2010-02-10 14:58       ` [PATCH v4 4/7] V4L: Events: Support event handling in do_ioctl Sakari Ailus
2010-02-10 14:58         ` [PATCH v4 5/7] V4L: Events: Count event queue length Sakari Ailus
2010-02-10 14:58           ` [PATCH v4 6/7] V4L: Events: Sequence numbers Sakari Ailus
2010-02-10 14:58             ` [PATCH v4 7/7] V4L: Events: Support all events Sakari Ailus
2010-02-13 14:42               ` Hans Verkuil
2010-02-15 10:11                 ` Laurent Pinchart
2010-02-15 10:36                   ` Hans Verkuil
2010-02-19 19:11                     ` Sakari Ailus
2010-02-13 14:18           ` [PATCH v4 5/7] V4L: Events: Count event queue length Hans Verkuil
2010-02-13 13:49         ` [PATCH v4 4/7] V4L: Events: Support event handling in do_ioctl Hans Verkuil
2010-02-15 10:05           ` Laurent Pinchart
2010-02-15 10:31             ` Hans Verkuil
2010-02-13 13:41       ` [PATCH v4 3/7] V4L: Events: Add backend Hans Verkuil
2010-02-13 13:19     ` [PATCH v4 2/7] V4L: Events: Add new ioctls for events Hans Verkuil
2010-02-15  9:55       ` Laurent Pinchart
2010-02-15 10:28         ` Hans Verkuil
2010-02-15 10:45           ` Laurent Pinchart
2010-02-13 13:10   ` [PATCH v4 1/7] V4L: File handles 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=4B72C965.7040204@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=david.cohen@nokia.com \
    --cc=gururaj.nagendra@intel.com \
    --cc=hverkuil@xs4all.nl \
    --cc=iivanov@mm-sol.com \
    --cc=laurent.pinchart@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox