Okay, found the reason why no hidraw was created.
hid_scan_report in hid-core.c sets the hid->group to
HID_GROUP_SENSOR_HUB for devices that use the sensor page.
hid-generic cannot bind to this device group, unless I add a second
entry to its hid_table, with group HID_GROUP_SENSOR_HUB.
Wouldn't it make sense to enable hidraw for sensor hubs too ?
cheers,
Matthias
On 21. 03. 13 15:28, Matthias Brändli wrote:
Dear group,
since recently, my custom USB HID Sensor gets bound to hid-sensor-hub,
and the /dev/hidraw1 node doesn't get created anymore. While this makes
sense, my test program still needs to access the device through hidraw.
What I've tested:
i) unbind from hid-sensor-hub
/sys/bus/hid/drivers/hid-sensor-hub #
echo -n "0003:1546:03A8.000A" > unbind
ii) bind to hid-generic (in the hope that this is the correct thing to do)
/sys/bus/hid/drivers/hid-generic #
echo -n "0003:1546:03A8.000A" > bind
echo: write error: no such device
(Rebinding to hid-sensor-hub works however)
Is this the correct way if I want a /dev/hidrawX to be created, or do I
also have to tell it udev in some way ?
Thanks in advance,
Matthias Brändli
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthias Brändli
R&D, Software Development
u-blox AG
Zuercherstrasse 68
8800 Thalwil
Switzerland
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
