public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: [Query] VIDIOC_QBUF and VIDIOC_STREAMON order
Date: Mon, 14 Mar 2011 11:14:00 +0100	[thread overview]
Message-ID: <4D7DEA68.2050604@samsung.com> (raw)

Hello,

As far as I know V4L2 applications are allowed to call VIDIOC_STREAMON before
queuing buffers with VIDIOC_QBUF.

This leads to situation that a H/W is attempted to be enabled by the driver
when it has no any buffer ownership. 

Effectively actual activation of the data pipeline has to be deferred
until first buffer arrived in the driver. Which makes it difficult 
to signal any errors to user during enabling the data pipeline.

Is this allowed to force applications to queue some buffers before calling
STREAMON, by returning an error in vidioc_streamon from the driver, when 
no buffers have been queued at this time?

I suppose this could render some applications to stop working if this kind
of restriction is applied e.g. in camera capture driver.

What the applications really expect?

With the above I refer mostly to a snapshot mode where we have to be careful
not to lose any frame, as there could be only one..


Please share you opinions.


Regards,
-- 
Sylwester Nawrocki
Samsung Poland R&D Center

             reply	other threads:[~2011-03-14 10:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 10:14 Sylwester Nawrocki [this message]
2011-03-14 10:49 ` [Query] VIDIOC_QBUF and VIDIOC_STREAMON order Subash Patel
2011-03-15  3:21   ` Pawel Osciak
2011-03-15  4:26     ` Subash Patel
2011-03-15  7:50     ` Hans Verkuil
2011-03-22 10:53       ` Laurent Pinchart
2011-03-22 23:58         ` Jonghun Han
     [not found] ` <AANLkTikBkPjy4jui1EjGULPFbUZxKK_ydaUqk7niFDxQ@mail.gmail.com>
2011-03-15 10:52   ` Sylwester Nawrocki

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=4D7DEA68.2050604@samsung.com \
    --to=s.nawrocki@samsung.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