From: Alan Ott <alan@signal11.us>
To: Randy Dunlap <rdunlap@xenotime.net>,
Jiri Kosina <jkosina@suse.cz>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Cc: Alan Ott <alan@signal11.us>
Subject: [PATCH v4 0/1] HID: Report Descriptor in Sysfs
Date: Sun, 23 Jan 2011 22:50:17 -0500 [thread overview]
Message-ID: <1295841018-8561-1-git-send-email-alan@signal11.us> (raw)
In-Reply-To: <20110123225935.GB12488@kroah.com>
This is version 4 of the patch, with Documentation as requested by Greg KH,
a version number fixed in the documentation, and sent to the right people
this time. (Sorry for the noise; I forgot to re-run get_maintainer.pl after
I added the docs for v3).
Original email follows:
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
next prev parent reply other threads:[~2011-01-24 3:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 6:19 [PATCH 0/1] HID: Report Descriptor in Sysfs Alan Ott
2011-01-21 6:19 ` [PATCH 1/1] hid: Add HID Report Descriptor to sysfs Alan Ott
2011-01-22 13:55 ` Greg KH
2011-01-23 22:35 ` [PATCH v2 0/1] HID: Report Descriptor in Sysfs Alan Ott
2011-01-23 22:35 ` [PATCH v2 1/1] hid: Add HID Report Descriptor to sysfs Alan Ott
2011-01-23 22:59 ` Greg KH
2011-01-24 0:36 ` [PATCH v3 0/1] HID: Report Descriptor in Sysfs Alan Ott
2011-01-24 0:36 ` [PATCH v3 1/1] hid: Add HID Report Descriptor to sysfs Alan Ott
2011-01-24 3:50 ` Alan Ott [this message]
2011-02-16 4:11 ` [PATCH v4 0/1] HID: Report Descriptor in Sysfs Alan Ott
2011-02-17 12:26 ` Jiri Kosina
2011-01-24 3:50 ` [PATCH v4 1/1] hid: Add HID Report Descriptor to sysfs Alan Ott
2011-02-17 12:55 ` Antonio Ospite
2011-01-21 9:59 ` [PATCH 0/1] HID: Report Descriptor in Sysfs Jiri Kosina
2011-01-21 14:52 ` Alan Ott
2011-01-21 15:09 ` Jiri Kosina
2011-01-21 15:29 ` Alan Ott
2011-01-21 16:14 ` Jiri Kosina
2011-01-21 16:57 ` Alan Ott
2011-01-21 20:03 ` Nikolai Kondrashov
2011-01-24 15:17 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295841018-8561-1-git-send-email-alan@signal11.us \
--to=alan@signal11.us \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).