Re: [PATCH 7/7] [media] gspca: fix a v4l2-compliance failure during read()

2016-03-14 Thread Antonio Ospite
On Thu, 10 Mar 2016 16:59:45 +0100 Hans de Goede wrote: > Hi, > > On 09-03-16 17:03, Antonio Ospite wrote: > > v4l2-compliance fails with this message: > > > >fail: v4l2-test-buffers.cpp(512): Expected EBUSY, got 22 > >test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: FAIL > > > > Looking at the

Re: [PATCH 7/7] [media] gspca: fix a v4l2-compliance failure during read()

2016-03-10 Thread Hans de Goede
Hi, On 09-03-16 17:03, Antonio Ospite wrote: v4l2-compliance fails with this message: fail: v4l2-test-buffers.cpp(512): Expected EBUSY, got 22 test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: FAIL Looking at the v4l2-compliance code reveals that this failure is about the read() callback. In gs

[PATCH 7/7] [media] gspca: fix a v4l2-compliance failure during read()

2016-03-09 Thread Antonio Ospite
v4l2-compliance fails with this message: fail: v4l2-test-buffers.cpp(512): Expected EBUSY, got 22 test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: FAIL Looking at the v4l2-compliance code reveals that this failure is about the read() callback. In gspca, dev_read() is calling vidioc_dqbuf() which ca