Searched refs:hiddev (Results 1 – 13 of 13) sorted by relevance
44 struct hiddev *hiddev; member143 struct hiddev *hiddev = hid->hiddev; in hiddev_send_event() local256 list->hiddev = hiddev; in __hiddev_open()279 hiddev->open--; in __hiddev_open()291 struct hiddev *hiddev; in hiddev_open() local299 hiddev = hid->hiddev; in hiddev_open()302 res = hiddev->exist ? __hiddev_open(hiddev, file) : -ENODEV; in hiddev_open()597 struct hiddev *hiddev = list->hiddev; in hiddev_ioctl() local877 struct hiddev *hiddev; in hiddev_connect() local900 hid->hiddev = hiddev; in hiddev_connect()[all …]
7 usbhid-$(CONFIG_USB_HIDDEV) += hiddev.o
35 bool "/dev/hiddev raw HID device support"
19 * the hiddev interface, which provides fairly raw HID events27 --> hiddev.c ----> POWER / MONITOR CONTROL36 The hiddev interface is a char interface using the normal USB major,57 So you point your hiddev compliant user-space program at the correct60 Assuming that you have a hiddev compliant user-space program, of71 The hiddev API uses a read() interface, and a set of ioctl() calls.84 returns to hiddev.c the individual usages that have changed within85 the report. In its basic mode, the hiddev will make these individual95 within <linux/hiddev.h>, along with some other useful #defines and110 Gets the version code out of the hiddev driver.
11 hiddev
6 Interface Devices (HIDs). It differs from hiddev in that reports sent and17 descriptors. Because hiddev parses reports which are sent and received19 communication with these non-conformant devices is impossible using hiddev.
23 struct hiddev { struct
662 void *hiddev; /* The hiddev structure */ member
191 the hiddev interface was designed. See Documentation/hid/hiddev.rst
2271 ((struct hiddev *)hdev->hiddev)->minor); in hid_connect()
55 There is also a /dev/hiddev configuration option in the USB HID56 configuration menu. In comparison to hiddev, this device does not process
145 'H' 00-7F linux/hiddev.h conflict!
25153 F: Documentation/hid/hiddev.rst