| /linux-4.1.27/Documentation/hid/ |
| D | hid-transport.txt | 1 HID I/O Transport Drivers
4 The HID subsystem is independent of the underlying transport driver. Initially,
5 only USB was supported, but other specifications adopted the HID design and
9 1) HID Bus
12 The HID subsystem is designed as a bus. Any I/O subsystem may provide HID
13 devices and register them with the HID bus. HID core then loads generic device
15 transport and device setup/management. HID core is responsible of
33 | HID Core |
46 Transport: USB-HID, I2C-HID, BT-HIDP
48 Everything below "HID Core" is simplified in this graph as it is only of
[all …]
|
| D | hid-sensor.txt | 2 HID Sensors Framework
4 HID sensor framework provides necessary interfaces to implement sensor drivers,
5 which are connected to a sensor hub. The sensor hub is a HID device and it provides
6 a report descriptor conforming to HID 1.12 sensor usage tables.
8 Description from the HID 1.12 "HID Sensor Usages" specification:
9 "Standardization of HID usages for sensors would allow (but not require) sensor
55 The core driver registers (hid-sensor-hub) registers as a HID driver. It parses
57 with name HID-SENSOR-xxxx (where xxxx is usage id from the specification).
59 HID-SENSOR-200073 is registered for an Accelerometer 3D driver.
80 int (*suspend)(..): Callback when HID suspend is received
[all …]
|
| D | uhid.txt | 1 UHID - User-space I/O driver support for HID subsystem
4 UHID allows user-space to implement HID transport drivers. Please see
5 hid-transport.txt for an introduction into HID transport drivers. This document
21 If a new device is detected by your HID I/O Driver and you want to register this
22 device with the HID subsystem, then you need to open /dev/uhid once for each
50 UHID_OPEN event, the internally attached HID Device Driver has no user attached.
53 user closes the HID device, you will receive an UHID_CLOSE event. This may be
56 UHID_OPEN events without an UHID_CLOSE event. The HID subsystem performs
61 If you want to send data on the interrupt channel to the HID subsystem, you send
90 This creates the internal HID device. No I/O is possible until you send this
[all …]
|
| D | hiddev.txt | 5 In addition to the normal input type HID devices, USB also uses the
12 HID events to two separate interfaces:
13 * the input subsystem, which converts HID events into normal input
16 * the hiddev interface, which provides fairly raw HID events
18 The data flow for a HID event produced by a device is something like
30 USING THE HID DEVICE INTERFACE
60 This description should be read in conjunction with the HID
66 HID devices exchange data with the host computer using data
72 This is the event interface. When the HID device's state changes,
84 containing the HID usage identifier for the status that changed, and
[all …]
|
| D | hidraw.txt | 6 received are not parsed by the HID parser, but are sent to and received from
10 communicate with the hardware device, and is able to construct the HID
12 custom HID devices.
14 Hidraw is also useful for communicating with non-conformant HID devices
25 use the HID specification, hidraw will be expanded to add support for these
41 read() will read a queued report received from the HID device. On USB
97 This ioctl will send a feature report to the device. Per the HID
|
| /linux-4.1.27/drivers/hid/ |
| D | Kconfig | 2 # HID driver configuration
4 menu "HID support"
7 config HID config
8 tristate "HID bus support"
12 A human interface device (HID) is a type of computer device that
13 interacts directly with and takes input from humans. The term "HID"
14 most commonly used to refer to the USB-HID specification, but other
16 designed using HID specification (this involves certain keyboards,
17 mice, tablets, etc). This option adds the HID bus to the kernel,
18 together with generic HID layer code. The HID devices are added and
[all …]
|
| /linux-4.1.27/drivers/iio/common/hid-sensors/ |
| D | Kconfig | 7 tristate "Common modules for all HID Sensor IIO drivers"
11 Say yes here to build support for HID sensor to use
12 HID sensor common processing for attributes and IIO triggers.
14 HID sensor drivers, this module contains processing for those
18 tristate "Common module (trigger) for all HID Sensor IIO drivers"
22 Say yes here to build trigger support for HID sensors.
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | configfs-usb-gadget-hid | 7 protocol - HID protocol to use
8 report_desc - blob corresponding to HID report descriptors
10 report_length - HID report length
11 subclass - HID device subclass to use
|
| D | sysfs-driver-hid | 7 Description: When read, this file returns the device's raw binary HID
19 of the device's HID country code (e.g. 21 for US).
|
| D | sysfs-driver-hid-picolcd | 13 Note: when switching mode the current PicoLCD HID device gets
|
| /linux-4.1.27/drivers/hid/usbhid/ |
| D | Kconfig | 1 menu "USB HID support"
5 tristate "USB HID transport layer"
8 select HID
11 mice, joysticks, graphic tablets, or any other HID based devices
24 comment "Input core support is needed for USB HID input layer or HIDBP support"
35 bool "/dev/hiddev raw HID device support"
38 Say Y here if you want to support HID devices (from the USB
47 menu "USB HID Boot Protocol drivers"
55 to use the generic HID driver for your USB keyboard and prefer
71 to use the generic HID driver for your USB mouse and prefer
|
| /linux-4.1.27/drivers/hid/i2c-hid/ |
| D | Kconfig | 1 menu "I2C HID support"
5 tristate "HID over I2C transport layer"
8 select HID
11 other HID based devices which is connected to your computer via I2C.
|
| /linux-4.1.27/drivers/iio/orientation/ |
| D | Kconfig | 14 tristate "HID Inclinometer 3D"
16 Say yes here to build support for the HID SENSOR
25 tristate "HID Device Rotation"
27 Say yes here to build support for the HID SENSOR
|
| /linux-4.1.27/Documentation/devicetree/bindings/hid/ |
| D | hid-over-i2c.txt | 1 * HID over I2C Device-Tree bindings
3 HID over I2C provides support for various Human Interface Devices over the
16 - hid-descr-addr: HID descriptor address
|
| /linux-4.1.27/Documentation/usb/ |
| D | gadget_hid.txt | 2 Linux USB HID gadget driver
6 The HID Gadget driver provides emulation of USB Human Interface
7 Devices (HID). The basic HID handling is done in the kernel,
8 and HID reports can be sent/received through I/O on the
11 For more details about HID, see the developer page on
18 HID function descriptors you want to use - E.G. something
74 You can add as many HID functions as you want, only limited by
80 some data to the kernel, if HID is a part of a gadget composed with
84 Send and receive HID reports
86 HID reports can be sent/received using read/write on the
[all …]
|
| D | functionfs.txt | 39 One can imagine a gadget that has an Ethernet, MTP and HID interfaces
50 whether it's FunctionFS designed for MTP ("mtp") or HID ("hid").
|
| D | gadget-testing.txt | 9 6. HID function
176 6. HID function
185 The HID function provides these attributes in its function directory:
187 protocol - HID protocol to use
188 report_desc - data to be used in HID reports, except data
190 report_length - HID report length
191 subclass - HID subclass to use
207 Testing the HID function
|
| D | proc_usb_info.txt | 225 speaker with an audio interface for playback, and a HID interface
328 I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=mouse
350 I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=mouse
|
| D | usb-serial.txt | 224 -Cypress HID->COM RS232 adapter
|
| /linux-4.1.27/net/bluetooth/hidp/ |
| D | Kconfig | 4 select HID
7 for HID reports. HIDP is required for the Bluetooth Human
|
| /linux-4.1.27/drivers/iio/magnetometer/ |
| D | Kconfig | 45 tristate "HID Magenetometer 3D"
47 Say yes here to build support for the HID SENSOR
|
| /linux-4.1.27/Documentation/input/ |
| D | bcm5974.txt | 38 with the HID driver, which, if not told otherwise, will find the standard
39 HID mouse and keyboard, and claim the whole device. To remedy, the usb
|
| D | input.txt | 103 handles all HID devices, and because there is a very wide variety of them,
104 and because the USB HID specification isn't simple, it needs to be this big.
109 However, USB uses HID also for monitor controls, speaker controls, UPSs,
118 detects everything automatically and when a HID device is inserted, it
127 For embedded systems, for mice with broken HID descriptors and just any
143 PenPartner, that one is handled by the HID driver. Although the Intuos and
144 Graphire tablets claim that they are HID tablets as well, they are not and
|
| D | yealink.txt | 34 hiddev0: USB HID v1.00 Device [Yealink Network Technology Ltd. VOIP USB Phone
|
| /linux-4.1.27/drivers/iio/light/ |
| D | Kconfig | 115 tristate "HID ALS"
117 Say yes here to build support for the HID SENSOR
129 tristate "HID PROX"
131 Say yes here to build support for the HID SENSOR
|
| /linux-4.1.27/drivers/iio/gyro/ |
| D | Kconfig | 71 tristate "HID Gyroscope 3D"
73 Say yes here to build support for the HID SENSOR
|
| /linux-4.1.27/drivers/iio/pressure/ |
| D | Kconfig | 25 tristate "HID PRESS"
27 Say yes here to build support for the HID SENSOR
|
| /linux-4.1.27/drivers/iio/accel/ |
| D | Kconfig | 41 tristate "HID Accelerometers 3D"
43 Say yes here to build support for the HID SENSOR
|
| /linux-4.1.27/drivers/acpi/acpica/ |
| D | nsxfeval.c | 785 acpi_get_devices(const char *HID, in acpi_get_devices() argument
804 info.hid = HID; in acpi_get_devices()
|
| /linux-4.1.27/drivers/usb/gadget/ |
| D | Kconfig | 420 bool "HID function"
424 The HID function driver provides generic emulation of USB
425 Human Interface Devices (HID).
|
| /linux-4.1.27/drivers/usb/gadget/legacy/ |
| D | Kconfig | 422 tristate "HID Gadget"
426 The HID gadget driver provides generic emulation of USB
427 Human Interface Devices (HID).
|
| /linux-4.1.27/Documentation/acpi/ |
| D | scan_handlers.txt | 32 basis of the device node's hardware ID (HID). They are performed by objects
|
| /linux-4.1.27/include/acpi/ |
| D | acpixf.h | 479 acpi_get_devices(const char *HID,
|
| /linux-4.1.27/drivers/macintosh/ |
| D | Kconfig | 166 Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
|
| /linux-4.1.27/drivers/input/joystick/ |
| D | Kconfig | 171 SpaceBall 4000 USB model, use the USB HID driver.
|
| /linux-4.1.27/arch/xtensa/configs/ |
| D | iss_defconfig | 466 # Special HID drivers
|
| /linux-4.1.27/drivers/rtc/ |
| D | Kconfig | 1543 comment "HID Sensor RTC drivers"
1546 tristate "HID Sensor Time"
1552 Say yes here to build support for the HID Sensors of type Time.
|
| /linux-4.1.27/drivers/leds/ |
| D | Kconfig | 501 comment "LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)"
|
| /linux-4.1.27/drivers/platform/x86/ |
| D | Kconfig | 663 found on recent Toshiba laptops equiped with HID TOS620A
|
| /linux-4.1.27/ |
| D | CREDITS | 1600 D: Author and maintainer of the Bluetooth HID protocol driver
1961 D: Generic HID layer - original code split, fixes
2781 D: USB (HID, ACM, Printer ...)
|
| D | MAINTAINERS | 4637 HID CORE LAYER
7675 PICOLCD HID DRIVER
10180 UHID USERSPACE HID IO DRIVER:
10311 USB HID/HIDBP DRIVERS (USB KEYBOARDS, MICE, REMOTE CONTROLS, ...)
10776 WIIMOTE HID DRIVER
|
| /linux-4.1.27/Documentation/ |
| D | devices.txt | 456 239 = /dev/uhid User-space I/O driver support for HID subsystem
2548 96 = /dev/usb/hiddev0 1st USB HID device
2550 111 = /dev/usb/hiddev15 16th USB HID device
|