From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sean V Kelley <sean.v.kelley@intel.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] uvcvideo: Implement videobuf2 .wait_prepare and .wait_finish operations
Date: Tue, 05 Feb 2013 10:08:52 +0100 [thread overview]
Message-ID: <1596838.QUSgh4fGy1@avalon> (raw)
In-Reply-To: <CA+qSnqj25NRCGXnS4-AJ34zpa+kOCTM--RY95Qfd0mZfcrhTHQ@mail.gmail.com>
Hi Sean,
On Monday 04 February 2013 12:36:47 Sean V Kelley wrote:
> On Mon, Jan 21, 2013 at 2:51 AM, Laurent Pinchart wrote:
> > Those optional operations are used to release and reacquire the queue
> > lock when videobuf2 needs to perform operations that sleep for a long
> > time, such as waiting for a buffer to be complete. Implement them to
> > avoid blocking qbuf or streamoff calls when a dqbuf is in progress.
>
> Speaking of UVC, are there plans to look into supporting UVC 1.5
> specification? Are you aware of any development in that area for new
> controls?
There's work in progress to implement UVC 1.5 but I'm not sure how much
details I can share. I should get a progress report in two weeks at the ELC in
San Francisco, will you happen to be there by any chance ?
You're the third Intel developer who contacts me about UVC in the last 3 days,
I assume that's not a coincidence. If you ever need consulting services on the
uvcvideo driver (or just if you think collaboration would be helpful) please
feel free to contact me.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-02-05 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 10:51 [PATCH] uvcvideo: Implement videobuf2 .wait_prepare and .wait_finish operations Laurent Pinchart
[not found] ` <CA+qSnqj25NRCGXnS4-AJ34zpa+kOCTM--RY95Qfd0mZfcrhTHQ@mail.gmail.com>
2013-02-05 9:08 ` Laurent Pinchart [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=1596838.QUSgh4fGy1@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sean.v.kelley@intel.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