Hi,
I have been trying to add the driver I have written for a sensor device built around msp430 and running TI USB Stack. The driver was working fine with 2.6 series kernel. Now in 3.2 and 3.4.4 I have noticed that if my device's report descriptor doesn't need a fixup, it doesn't even call my driver's functions. It just gives me a message like
I have been trying to add the driver I have written for a sensor device built around msp430 and running TI USB Stack. The driver was working fine with 2.6 series kernel. Now in 3.2 and 3.4.4 I have noticed that if my device's report descriptor doesn't need a fixup, it doesn't even call my driver's functions. It just gives me a message like
Jul 3 16:31:05 subin kernel: [23295.709199] generic-usb 0003: DEAD: BEEF.0009: hiddev0,hidraw0: USB HID v1.01 Device [USB HID Sensor] on usb-0000:00:1d.3-2/input0And doesn't poll the device. When I purposefully add something like an invalid logical maximum or something in report descriptor, it calls the fixup function, probe and events. All going good. I have seen the entries in drivers/hid/hid-core.c for the devices which have a driver. But in my running kernel, I can not add my device to this list. Am I missing something? Is there a way to prevent the hiddev and hidraw taking control on my device?