Kid <> wrote:
>
>Do you mean USB always us the way of polling ?
No, it's more complicated than that. USB is a protocol bus, and the
bandwidth is shared amongst all of the devices on the bus. The USB
hardware does use interrupts to let the host controller driver know that
there are things to handle. That driver will then notify USB client
drivers that their requests have completed.
So, effectively, a USB client driver can pretend that it is getting
interrupts, but they appear as the completion routine for the requests it
submits.
>So I should get the input data inside io control function ?
There are well-defined ways of filtering mouse and keyboard events, some of
which don't require a driver at all. It depends what you need your filter
to do.
--
Tim Roberts,
Providenza & Boekelheide, Inc.