Hi,
I am writing a USB driver that uses both bulk and interrupt transfers.
Since I have no experience in writing drivers on Linux, I looked at the code
of
some existing driver and adjusted the code to fit my needs.
In the probe() function I noticed that the interrupt pipe is initialized by:
FILL_INT_URB(&data->irq_event, dev,
usb_rcvintpipe(dev, 1),
&data->intr_event, 8, irq_event_callback, data,
endpoint[1].bInterval);
if (usb_submit_urb(&data->reader_irq_event)) {
err("probe: Unable to allocate INT URB.");
kfree(data);
return NULL;
}
I guess this is done that way because no usb_intr_msg() function exists.
Is it a normal behavior that the callback function is called whenever some
data
is sent in the interrupt pipe? Does it mean that the kernel (as a usb host)
initiates
an interrupt request every bInterval?
The problem is that I dont want to count on the kernel behavior but want to
initiate an
interrupt transfer myself (as it's done for the bulk pipe). Is it possible?
Thanks,
Amira.
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
