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>,
	Guru Raj <gururaj.nagendra@intel.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Mike Krufky <mkrufky@linuxtv.org>,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	"Ivan T. Ivanov" <iivanov@mm-sol.com>,
	Zutshi Vimarsh <vimarsh.zutshi@nokia.com>
Subject: [RFC 0/4] V4L2 file handles and event interface
Date: Tue, 15 Dec 2009 14:12:26 +0200	[thread overview]
Message-ID: <4B277D2A.7050201@maxwell.research.nokia.com> (raw)

Hi,

Here's the first version of the V4L2 file handle and event interface 
patchset. I posted it as RFC since there are a few issues with the 
contents and I have no assurrances that this even is functional at the 
moment.

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

A few notes on the patches:

- I don't like the locking too much. Perhaps the file handle specific 
lock (events->lock) could be dropped in favour of the lock for 
v4l2_file_handle in video_device.

- Event queue depth is not controlled at the moment.

- (Un)subscribing all events is not supported.

Comments are very welcome.

Cheers,

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




             reply	other threads:[~2009-12-15 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 12:12 Sakari Ailus [this message]
2009-12-15 12:19 ` [RFC 1/4] V4L: File handles Sakari Ailus
2009-12-15 12:19   ` [RFC 2/4] V4L: Events: Add new ioctls for events Sakari Ailus
2009-12-15 12:19     ` [RFC 3/4] V4L: Events: Support event handling in do_ioctl Sakari Ailus
2009-12-15 12:19       ` [RFC 4/4] V4L: Events: Add backend Sakari Ailus

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=4B277D2A.7050201@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=dheitmueller@kernellabs.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 \
    --cc=mchehab@infradead.org \
    --cc=mkrufky@linuxtv.org \
    --cc=vimarsh.zutshi@nokia.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