projects / platform / upstream / v4l-utils.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: eeceb4b) | patch
v4l2-compliance: allow EIO for control ioctls
authorHans Verkuil <hans.verkuil@cisco.com>
Fri, 8 Aug 2014 09:04:50 +0000 (11:04 +0200)
committerHans Verkuil <hans.verkuil@cisco.com>
Fri, 8 Aug 2014 09:04:50 +0000 (11:04 +0200)
commit48c8f3b4371afc02b57c525e1691cd4090f91261
tree4396d2122db2b8c5696fd94f37b1fa3c62a5c26dtree | snapshot
parenteeceb4b2e148f29fe1a46f3c25199c35fc39868bcommit | diff
v4l2-compliance: allow EIO for control ioctls

The uvc driver has to pass on the new control values to the hardware,
and that may not always accept the new value, even though it was
reported as within the valid range. In that case EIO is returned
and v4l2-compliance should accept that as a valid error code. It's
not the uvc driver's fault that there are many devices with crappy
firmware.

Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
utils/v4l2-compliance/v4l2-test-controls.cpp diff | blob | history
Domain: Multimedia / Media Camera;