Re: [PATCH 0/1] HID: Report Descriptor in Sysfs

From: Jiri Kosina
Date: Fri Jan 21 2011 - 05:00:00 EST


On Fri, 21 Jan 2011, 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?

Hi Alan,

the report descriptor is provided through debugfs HID interface already.
Do you feel like that's not enough?

Thanks,

--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/