[PATCH v3 0/6] hid: Introduce device groups

From: Henrik Rydberg
Date: Mon Apr 23 2012 - 06:03:40 EST

Hi Jiri,

Here is the third version of the extension to the device-driver
matching mechanism. AFAICT, there are no outstanding issues. I think
we are getting close. :-)

Building on the report fixup patches, this patchset brings a bit of
transparency to the hid bus, by the addition of device groups. This
allows a more versatile handling of hid drivers in userland, and
simplifies the logic in the kernel.

In particular, there can be one generic module per device group, and
those modules are handled automatically by udev. Dynamic rebinding of
drivers is fully supported. For instance, to load a special
out-of-tree driver instead of the a generic one, simply unbind the
device and load the new module. One can also keep _all_ generic
drivers as modules, significantly simplifying the process of adding
and testing new features.

And, of course, auto-loading of new multitouch drivers works, since
that was what triggered this patchset to begin with. :-)

The second patch contains a simple descriptor scanner that is
new. The last patch unifies the generic drivers into a single,
loadable module.


Henrik Rydberg (6):
hid: Add device group to modalias
hid: Scan the device for group info before adding it
hid: Allow bus wildcard matching
hid: Create a generic device group
hid-multitouch: Switch to device groups
hid: Create a common generic driver

drivers/hid/Kconfig | 12 +++
drivers/hid/Makefile | 2 +
drivers/hid/hid-core.c | 172 ++++++++++++++++++++-------------------
drivers/hid/hid-generic.c | 53 ++++++++++++
drivers/hid/hid-input.c | 11 ---
drivers/hid/hid-multitouch.c | 3 +-
drivers/hid/usbhid/hid-core.c | 16 ----
include/linux/hid.h | 20 +++--
include/linux/mod_devicetable.h | 4 +-
net/bluetooth/hidp/core.c | 27 +-----
scripts/mod/file2alias.c | 5 +-
11 files changed, 180 insertions(+), 145 deletions(-)
create mode 100644 drivers/hid/hid-generic.c

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/