blob: 6ef476a5401652a8be457e14ec8a0e0f38759d59 [file] [log] [blame]
Mauro Carvalho Chehab6d172492011-07-05 10:07:37 -03001<title>Generic Error Codes</title>
2
3<table frame="none" pgwide="1" id="gen-errors">
4 <title>Generic error codes</title>
5 <tgroup cols="2">
6 &cs-str;
7 <tbody valign="top">
8 <row>
9 <entry>EBUSY</entry>
10 <entry>The ioctl can't be handled because the device is busy. This is
11 typically return while device is streaming, and an ioctl tried to
12 change something that would affect the stream, or would require the
Mauro Carvalho Chehab43c1daa2011-07-05 11:22:28 -030013 usage of a hardware resource that was already allocated. The ioctl
14 must not be retried without performing another action to fix the
15 problem first (typically: stop the stream before retrying).</entry>
16 </row>
17 <row>
18 <entry>EINVAL</entry>
19 <entry>The ioctl is not supported by the driver, actually meaning that
20 the required functionality is not available.</entry>
21 </row>
22 <row>
23 <entry>ENOMEM</entry>
24 <entry>There's not enough memory to handle the desired operation.</entry>
25 </row>
26 <row>
27 <entry>ENOSPC</entry>
28 <entry>On USB devices, the stream ioctl's can return this error meaning
29 that this request would overcommit the usb bandwidth reserved
30 for periodic transfers (up to 80% of the USB bandwidth).</entry>
Mauro Carvalho Chehab6d172492011-07-05 10:07:37 -030031 </row>
32 </tbody>
33 </tgroup>
34</table>