[lkml]   [2007]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [linux-usb-devel] [RFC] HID bus design overview.
    On Mon, 2 Apr 2007, Marcel Holtmann wrote:

    > I like this idea, but it might not solve the case where you have parts
    > of the driver in kernel space and other parts in user space. For example
    > the control of a LCD display on the keyboard. However in most cases
    > registering drivers for a report id should be enough.

    Hi Marcel,

    the specialized driver could hook on all reports of the device (as
    discussed a few mails ago in this thread) and have the possibility to do
    three different things with the obtained report:

    - pass it back to generic hid driver for "standard" processing
    - process the report, and issue input_event() itself
    - pass it to hidraw and let userspace to consume it

    This is going to work for the scenario you have described, right?


    Jiri Kosina
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-04-02 14:31    [W:0.018 / U:22.900 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site