On 01/23/2011 10:50 PM, Alan Ott wrote:
So I'd like to have access to the HID report descriptor in a sysfs entry, so I can read it without opening the device. hid-core seemed like the place to put it. Using the /sys/class links, for hidraw devices, this puts a new file, report_descriptor in the directory: /sys/class/hidraw/hidraw0/device/ For my USB device (for example), the new file is in: /sys/bus/usb/devices/1-5.3:1.0/0003:046D:C216.0001/ For my Bluetooth device, the new file is in: /sys/class/bluetooth/hci0/hci0:11/0005:054C:0268.0002/ I'm not super confident that these file locations are the best place, but I made a best guess so that it could be discussed. The current location is where the hid-core stuff lives. Is there a reason these directories are named bus:vendor:product:id (instead of hid-core or something similar)? Is there a better way to do this? Alan. Alan Ott (1): hid: Add HID Report Descriptor to sysfs. Documentation/ABI/testing/sysfs-driver-hid | 10 ++++++++ drivers/hid/hid-core.c | 33 ++++++++++++++++++++++++++++ 2 files changed, 43 insertions(+), 0 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-driver-hid
I Didn't get any responses on the fixed-up patch. Does anyone have any issue with this?
Alan. -- 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
