From: Andy Walls <awalls@md.metrocast.net>
To: Ben Collins <benmcollins13@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Request clarification on videobuf irqlock and vb_lock usage
Date: Sat, 26 Feb 2011 23:08:02 -0500 [thread overview]
Message-ID: <1298779682.2423.10.camel@localhost> (raw)
In-Reply-To: <022EECA1-5416-4173-B435-348531BB5049@gmail.com>
On Sat, 2011-02-26 at 13:57 -0500, Ben Collins wrote:
> I'm trying to cleanup some deadlocks and random crashed in my v4l2
> driver (solo6x10) and I cannot find definitive documentation on that
> clear usage of irqlock and vb_lock in a driver that uses videobuf.
Here is the best documentation on videobuf(1) that I ever saw:
http://git.linuxtv.org/media_tree.git?a=blob;f=Documentation/video4linux/videobuf;h=17a1f9abf260f39a44dee35bf7b72a0c66fd71fc;hb=df37e8479875c486d668fdf5bf65dba41422dd76
And here is the bad news about videobuf(1):
http://linuxtv.org/downloads/presentations/summit_jun_2010/20100614-v4l2_summit-videobuf.pdf
Since videobuf2 in now in the bleeding edge kernel, you should look at
using it:
http://lwn.net/Articles/420512/
http://linuxtv.org/downloads/presentations/summit_jun_2010/Videobuf_Helsinki_June2010.pdf
Tonight, I've actually been xamining using videobuf2 for cx18 myself.
> When and where should I be using either of these to ensure I work synchronously with the videobuf-core?
Maybe the above briefs, that detail some of the problems with
videobuf(1), can provide some details on the semantics of them. IIRC,
Pawel's brief highlighted that iolock was really overloaded.
Regards,
Andy
> --
> Bluecherry: http://www.bluecherrydvr.com/
> SwissDisk : http://www.swissdisk.com/
> Ubuntu : http://www.ubuntu.com/
> My Blog : http://ben-collins.blogspot.com/
prev parent reply other threads:[~2011-02-27 4:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 18:57 Request clarification on videobuf irqlock and vb_lock usage Ben Collins
2011-02-27 4:08 ` Andy Walls [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=1298779682.2423.10.camel@localhost \
--to=awalls@md.metrocast.net \
--cc=benmcollins13@gmail.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;
as well as URLs for NNTP newsgroup(s).