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>,
	Cohen David Abraham <david.cohen@nokia.com>
Subject: [PATCH v6 0/6] V4L2 file handles and event interface
Date: Mon, 22 Feb 2010 17:51:23 +0200	[thread overview]
Message-ID: <4B82A7FB.50505@maxwell.research.nokia.com> (raw)

Hi,

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

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

The patchset I'm posting now is against the v4l-dvb tree instead of
linux-omap. The omap3camera tree thus has a slightly different
version of these patches due to different baselines.

Some more comments from Hans and Laurent. What has changed:

- Improved documentation.
- V4L2_EVENT_ALL only valid in unsubscribing.
- Events are initialised in v4l2_fh_init() if
video_device->ioctl_ops->vidioc_subscribe_event is defined.
- Event ioctl handlers are called in __video_do_ioctl() iff
video_device->ioctl_ops->vidioc_subscribe_event is defined, no other
constraints.
- Blocking operation for VIDIOC_DQEVENT.
- v4l2_event_subscribe_many() is gone.
- Fixed memory leak in v4l2_event_subscribe()

Comments are welcome as always.

Cheers,

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


             reply	other threads:[~2010-02-22 15:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 15:51 Sakari Ailus [this message]
2010-02-22 15:51 ` [PATCH 1/6] V4L: File handles Sakari Ailus
2010-02-22 15:51   ` [PATCH 2/6] V4L: File handles: Add documentation Sakari Ailus
2010-02-22 15:51     ` [PATCH 3/6] V4L: Events: Add new ioctls for events Sakari Ailus
2010-02-22 15:51       ` [PATCH 4/6] V4L: Events: Add backend Sakari Ailus
2010-02-22 15:51         ` [PATCH 5/6] V4L: Events: Support event handling in do_ioctl Sakari Ailus
2010-02-22 15:51           ` [PATCH 6/6] V4L: Events: Add documentation Sakari Ailus
2010-02-22 19:57             ` Hans Verkuil
2010-02-22 22:47               ` Sakari Ailus
2010-02-22 23:20                 ` Hans Verkuil
2010-02-22 23:27                   ` Sakari Ailus
2010-02-23  7:19                     ` Hans Verkuil
2010-02-23  7:55                       ` Sakari Ailus
2010-02-22 20:02           ` [PATCH 5/6] V4L: Events: Support event handling in do_ioctl Hans Verkuil
2010-02-22 19:58         ` [PATCH 4/6] V4L: Events: Add backend Hans Verkuil
2010-02-22 19:58       ` [PATCH 3/6] V4L: Events: Add new ioctls for events Hans Verkuil
2010-02-22 19:58     ` [PATCH 2/6] V4L: File handles: Add documentation Hans Verkuil
2010-02-22 16:00   ` [PATCH 1/6] V4L: File handles Sakari Ailus
2010-02-22 19:57   ` 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=4B82A7FB.50505@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=david.cohen@nokia.com \
    --cc=hverkuil@xs4all.nl \
    --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