Hi On Wed, Jun 26, 2013 at 5:45 PM, <michael.banken@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > The idea was to make the creation of an empty hid device while inside the > kernel easier. This problem came up, when I was writing a kernel module > driver for a usb temperature sensor. The sensors were supposed to be > recognized in lm-sensors, which does not recognize usb devices. The > solution in this case was to create an empty hid device to hook it up to > sysfs. > In some older implementations of this driver the solution to this problem > was creating an empty hid device to hook it up to sysfs. > These older implementations of the driver are not working anymore, unless > built with the change I am suggesting, because in the current version > their method of creating the hid device causes a NULL pointer dereference > at the point where I added the check. So you create an empty HID device to achieve what? I really cannot follow, sorry. If you want lm_sensors to pick up your sensors, why not patch lm_sensors to do so? > The reason, why I believe this change to be completely harmless is that in > the case where there actually is a NULL pointer the function would > dereference it anyway immediately after the line where I added the check. > The only problem that to my understanding could possibly arise is delaying > the inevitable oops for a little while. All other parts of the HID layer assume ll_driver to be NULL. It works for you, because you avoid any ll_driver interaction so these parts of the HID core that work with it will never get called. However, that's not how it is supposed to work. Could you describe why you cannot hook up your device as USB device directly? Does lm_sensors only scan HID bus devices, not USB bus devices or what is the exact reason? > best regards, > Michael Cheers David -- 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
