Re: Interacting with a input kernel driver from user space

[Nuno Santos <nsantos@xxxxxxxxxx>]

But my device isn't an HID device. My device is a vendor specific device:

bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0


I need bulk transfers for data in and out.

--

Right. Unless we are talking about haptic feedback or leds, information 
really flows one way, so there should be no reason to send anything back 
to the kernel. For detected but anonymous touches, we have MT protocol A 
in the input subsystem. If your raw data does not even contain detected 
touches, I would try hidraw, as Dmitry suggested. Thanks, Henrik


--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html