Laurent Pinchart wrote:
[clip]
If I'm not mistaken videobuf_dqbuf() only returns -EIO if the buffer state is
VIDEOBUF_ERROR. This is the direct result of either
- videobuf_queue_cancel() being called, or
- the device driver marking the buffer as erroneous because of a (possibly
transient) device error
In the first case VIDIOC_DQBUF should in my opinion return with an error. In
the second case things are not that clear. A transient error could be hidden
from the application, or, if returned to the application through -EIO,
shouldn't be treated as a fatal error. Non-transient errors should result in
the application stopping video streaming.
Unfortunately there V4L2 API doesn't offer a way to find out if the error is
transient or fatal:
"EIO VIDIOC_DQBUF failed due to an internal error. Can also indicate
temporary problems like signal loss. Note the driver might dequeue an (empty)
buffer despite returning an error, or even stop capturing."
-EIO can mean many different things that need to be handled differently by
applications. I especially hate the "the driver might dequeue an (empty)
buffer despite returning an error".
Drivers should always or never dequeue a buffer when an error occurs, not
sometimes. The problem is for the application to recognize the difference
between a transient and a fatal error in a backward-compatible way.
The errors in this case are transient and for blocking mode IMO the
safest way is to return the buffer only when there's one available.
Which is what the driver is doing now.
What I'd probably change, however, is to move the handling to the ISP
driver instead.
Regards,
--
Sakari Ailus
sakari.ailus@xxxxxxxxxxxxxxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
