diff options
author | Jason Gerecke <killertofu@gmail.com> | 2017-07-24 09:46:18 -0700 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2017-07-27 15:14:28 +0200 |
commit | fc2237a724a9e448599076d7d23497f51e2f7441 (patch) | |
tree | 0f6fc077d1452bba1d2e690d08f6bef622f20919 /net/bluetooth/hidp | |
parent | bc35f73aa62f51b80f769d3a6617f4a4ba11d81e (diff) | |
download | linux-fc2237a724a9e448599076d7d23497f51e2f7441.tar.gz linux-fc2237a724a9e448599076d7d23497f51e2f7441.tar.bz2 linux-fc2237a724a9e448599076d7d23497f51e2f7441.zip |
HID: introduce hid_is_using_ll_driver
Although HID itself is transport-agnostic, occasionally a driver may
want to interact with the low-level transport that a device is connected
through. To do this, we need to know what kind of bus is in use. The
first guess may be to look at the 'bus' field of the 'struct hid_device',
but this field may be emulated in some cases (e.g. uhid).
More ideally, we can check which ll_driver a device is using. This
function introduces a 'hid_is_using_ll_driver' function and makes the
'struct hid_ll_driver' of the four most common transports accessible
through hid.h.
Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
Acked-By: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'net/bluetooth/hidp')
-rw-r--r-- | net/bluetooth/hidp/core.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/net/bluetooth/hidp/core.c b/net/bluetooth/hidp/core.c index 002743ea509c..8112893037bd 100644 --- a/net/bluetooth/hidp/core.c +++ b/net/bluetooth/hidp/core.c @@ -734,7 +734,7 @@ static void hidp_stop(struct hid_device *hid) hid->claimed = 0; } -static struct hid_ll_driver hidp_hid_driver = { +struct hid_ll_driver hidp_hid_driver = { .parse = hidp_parse, .start = hidp_start, .stop = hidp_stop, @@ -743,6 +743,7 @@ static struct hid_ll_driver hidp_hid_driver = { .raw_request = hidp_raw_request, .output_report = hidp_output_report, }; +EXPORT_SYMBOL_GPL(hidp_hid_driver); /* This function sets up the hid device. It does not add it to the HID system. That is done in hidp_add_connection(). */ |