How to match hid device to our hid driver

[guo jerry]

Thanks Greg, I am very appreciate for your reply, and I know what to do in
the following.
Next time, if I have problems about linux USB device drivers, I will ask on
linux-usb mailing list.
Now I am on vacation of the Chinese Dragon Boat Festival. I think I'll be
very happy when going back to work on next Monday. :)

The project which I work on is implementing a multi-touch touch panel
driver.
And the device is a hid digitizer type, it's single touch panel default.
In order to enable it's multi-touch ability, we need to send set_report
command to work in multi-touch mode.
And then, device will send two points to device driver.

The problem is that device event don't work correctly in single touch mode.
I have added some printk messages in evdev_event, the messages showing that
the event type which evdev_event is got
are not correct. Evdev_event only got y and z axies, and dont't get x. But
what I am confusing is that the device work correctly
on Windows 7 and without any driver.

On the other side, in order to enable the multi-touch mode. I need to send
set_report command to the digitizer device.
After that, I need to  get the new report descriptor, when I get it ,I need
to create two input device node and attach to
myown input handler .And then when new report data comes, I need to parse it
and send corresponding event to each node.

I don't know if the hid protocol support this kind of mechanism, so I try to
implement a new hid driver, may be it would be a easy
way to do it by myself??

thanks,
Zhe Yao, Guo

2009/5/28 Greg KH <greg at kroah.com>

> On Thu, May 28, 2009 at 09:52:42PM +0800, guo jerry wrote:
> > Is there anyone know how to match hid device to hid driver which is
> > written by ourself.
> >
> > the problem is that my hid device always match with default hid driver
> > generic-usb.
> >
> > I don't know how to match my hid device with my hid driver.
>
> You should ask this on the linux-usb mailing list, after reading the
> archives which contains a description of how to do this (hint, add your
> device to the hid blacklist, and then your driver will bind to it.)
>
> Why do you want to use your driver instead of the Linux hid driver?  Is
> your device not a "real" HID device?
>
> thanks,
>
> greg k-h
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/kernel-mentors/attachments/20090529/de6dbfa3/attachment.htm