original_kernel/drivers/usb/misc
Marcin Slusarz 6def755320 usbtest: comment on why this code "expects" negative and positive errnos
On Mon, May 12, 2008 at 01:02:22AM -0700, David Brownell wrote:
> On Sunday 11 May 2008, Marcin Slusarz wrote:
> > 
> > test_ctrl_queue expects (?) positive and negative errnos.
> > what is going on here?
> 
> The sign is just a way to flag something:
> 
>                 /* some faults are allowed, not required */
> 
> The negative ones are required.  Positive codes are optional,
> in the sense that, depending on how the peripheral happens
> to be implemented, they won't necessarily be triggered.
> 
> For example, the test to fetch a device qualifier desriptor
> must succeed if the device is running at high speed.  So that
> test is marked as negative.  But when it's full speed, it
> could legitimately fail; marked as positive.  And so on for
> other tests.
> 
> Look at how the codes are *interpreted* to see it work.

Lets document it.

Based on comment from David Brownell <david-b@pacbell.net>.

Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: David Brownell <david-b@pacbell.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-05-14 10:00:29 -07:00
..
sisusbvga
Kconfig
Makefile
adutux.c
appledisplay.c
auerswald.c
berry_charge.c
cypress_cy7c63.c
cytherm.c
emi26.c
emi26_fw.h
emi62.c
emi62_fw_m.h
emi62_fw_s.h
ftdi-elan.c
idmouse.c
iowarrior.c
ldusb.c
legousbtower.c
phidget.c
phidget.h
phidgetkit.c
phidgetmotorcontrol.c
phidgetservo.c
rio500.c
rio500_usb.h
trancevibrator.c
usb_u132.h
usblcd.c
usbled.c
usbtest.c
uss720.c