From: Alexander Holler <holler-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
To: linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
srinivas.pandruvada-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
matteo.dameno-qxv4g6HH51o@public.gmane.org
Subject: hid-sensor-hub and autoloading of HID sensor modules
Date: Mon, 10 Dec 2012 22:07:53 +0100 [thread overview]
Message-ID: <50C64F29.9030200@ahsoftware.de> (raw)
Hello,
as I've just posted a patch to get rid of the vendor and device IDs for
USB HID sensor hubs, there is still one problem left: hid-sensor-hub
doesn't automatically load the necessary drivers (if they are modules).
Here is a suggestion about how to solve that:
Create HID groups HID_GROUP_SENSOR_ACCEL, HID_GROUP_SENSOR_TIME, ...)
for every type of (supported) sensor (instead of the one
HID_GROUP_SENSOR_HUB), scan for their usage pages (e.g.
HID_USAGE_SENSOR_ACCEL, HID_USAGE_SENSOR_TIME, ...) set the group and so
load the final module and not hid-sensor-hub. hid-sensor-hub will then
get loaded automatically.
As I don't have any real sensor hubs (and no business with them), I
think others should implement such, if that idea got approved to make
sense. ;)
That just would be some few lines, but I couldn't test them with
real-world stuff.
Regards,
Alexander
next reply other threads:[~2012-12-10 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 21:07 Alexander Holler [this message]
[not found] ` <50C64F29.9030200-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
2012-12-10 21:22 ` hid-sensor-hub and autoloading of HID sensor modules Pandruvada, Srinivas
[not found] ` <4FA419E87744DF4DAECD5BCE1214B7A91C96075E-P5GAC/sN6hk8Ug9VwtkbtrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-12-10 21:33 ` Alexander Holler
2012-12-10 21:40 ` Pandruvada, Srinivas
2012-12-10 21:53 ` Alexander Holler
[not found] ` <50C659C1.7060005-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
2012-12-11 18:34 ` Alexander Holler
2012-12-11 18:40 ` Pandruvada, Srinivas
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=50C64F29.9030200@ahsoftware.de \
--to=holler-sxc+2es9fhnfweyvqqpykw@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matteo.dameno-qxv4g6HH51o@public.gmane.org \
--cc=srinivas.pandruvada-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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).