| /linux-6.6.21/Documentation/hid/ |
| D | amd-sfh-hid.rst | 7 The solution is working well on several OEM products. AMD SFH uses HID over PCIe bus.
9 the HID reports are generated as part of the kernel driver.
17 | HID User Space Applications |
22 | HID Core |
26 | AMD HID Transport |
30 | AMD HID Client |
31 | with HID Report Generator|
45 AMD HID Transport Layer
49 sensor data. The layer, which binds each device (AMD SFH HID driver) identifies the device type and
50 registers with the HID core. Transport layer attaches a constant "struct hid_ll_driver" object with
[all …]
|
| D | hid-transport.rst | 2 HID I/O Transport Drivers
5 The HID subsystem is independent of the underlying transport driver. Initially,
6 only USB was supported, but other specifications adopted the HID design and
10 1) HID Bus
13 The HID subsystem is designed as a bus. Any I/O subsystem may provide HID
14 devices and register them with the HID bus. HID core then loads generic device
16 transport and device setup/management. HID core is responsible for
36 | HID Core |
50 - Transport: USB-HID, I2C-HID, BT-HIDP
52 Everything below "HID Core" is simplified in this graph as it is only of
[all …]
|
| D | hidintro.rst | 4 Introduction to HID report descriptors
7 This chapter is meant to give a broad overview of what HID report
9 with HID devices that are not working well with Linux.
24 HID stands for Human Interface Device, and can be whatever device you
28 Many HID devices work out the box, even if their hardware is different.
35 This is because modern HID devices do advertise their capabilities
36 through the *HID report descriptor*, a fixed set of bytes describing
37 exactly what *HID reports* may be sent between the device and the host
39 a HID Report Descriptor may specify that "in a report with ID 3 the
42 The HID report itself then merely carries the actual data values
[all …]
|
| D | hid-sensor.rst | 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
51 - Core HID driver
56 The core driver (hid-sensor-hub) registers as a HID driver. It parses
58 with name HID-SENSOR-xxxx (where xxxx is usage id from the specification).
62 HID-SENSOR-200073 is registered for an Accelerometer 3D driver.
[all …]
|
| D | hid-bpf.rst | 4 HID-BPF
7 HID is a standard protocol for input devices but some devices may require
10 existing HID interfaces.
17 When (and why) to use HID-BPF
20 There are several use cases when using HID-BPF is better
30 With HID-BPF, we can apply this filtering in the kernel directly so userspace
38 HID-BPF allows the userspace program to load the program itself, ensuring we
44 In the HID tree, half of the drivers only fix one key or one byte
61 channels of communication that our HID and input stack do not support.
70 The kernel has a relatively static mapping of HID items to evdev bits.
[all …]
|
| D | uhid.rst | 2 UHID - User-space I/O driver support for HID subsystem
5 UHID allows user-space to implement HID transport drivers. Please see
6 hid-transport.rst for an introduction into HID transport drivers. This document
22 If a new device is detected by your HID I/O Driver and you want to register this
23 device with the HID subsystem, then you need to open /dev/uhid once for each
51 UHID_OPEN event, the internally attached HID Device Driver has no user attached.
54 user closes the HID device, you will receive a UHID_CLOSE event. This may be
57 UHID_OPEN events without a UHID_CLOSE event. The HID subsystem performs
62 If you want to send data on the interrupt channel to the HID subsystem, you send
91 This creates the internal HID device. No I/O is possible until you send this
[all …]
|
| D | hidreport-parsing.rst | 4 Manual parsing of HID report descriptors
7 Consider again the mouse HID report descriptor
27 ---- Length of data (see HID spec 6.2.2.2)
29 ------ Type of the item (see HID spec 6.2.2.2, then jump to 6.2.2.7)
31 --------- Function of the item (see HID spec 6.2.2.7, then HUT Sec 3)
45 (``0000``) is given in the HID spec Sec. 6.2.2.8 "Local Items", so that
|
| D | intel-ish-hid.rst | 10 There are many vendors providing external sensor hubs conforming to HID
17 These ISH also comply to HID sensor specification, but the difference is the
19 mainly use HID over I2C or USB. But ISH doesn't use either I2C or USB.
28 | USB HID | --> | ISH HID |
53 HID sensor applications, sensor calibration applications or sensor firmware
59 (ISH HID driver) identifies the device type and registers with the HID core.
78 | HID Sensor Hub MFD |
81 | HID Core |
84 | HID over ISH Client |
224 The size of ring can be specified by the client. HID client sets 16 and 32 for
[all …]
|
| D | hiddev.rst | 8 In addition to the normal input type HID devices, USB also uses the
15 HID events to two separate interfaces:
16 * the input subsystem, which converts HID events into normal input
19 * the hiddev interface, which provides fairly raw HID events
21 The data flow for a HID event produced by a device is something like
30 events into the input subsystem, but these have no effect on the HID
33 Using the HID Device Interface
67 This description should be read in conjunction with the HID
73 HID devices exchange data with the host computer using data
81 This is the event interface. When the HID device's state changes,
[all …]
|
| D | hidraw.rst | 7 received are not parsed by the HID parser, but are sent to and received from
11 communicate with the hardware device, and is able to construct the HID
13 custom HID devices.
15 Hidraw is also useful for communicating with non-conformant HID devices
26 use the HID specification, hidraw will be expanded to add support for these
44 read() will read a queued report received from the HID device. On USB
114 This ioctl will send a feature report to the device. Per the HID
136 In most cases, setting an input HID report on a device is meaningless and has
|
| /linux-6.6.21/drivers/hid/surface-hid/ |
| D | Kconfig | 2 menu "Surface System Aggregator Module HID support"
7 tristate "HID transport driver for Surface System Aggregator Module"
11 Driver to support integrated HID devices on newer Microsoft Surface
14 This driver provides support for the HID transport protocol provided
20 Say M or Y here, if you want support for integrated HID devices, i.e.
25 tristate "HID keyboard transport driver for Surface System Aggregator Module"
28 Driver to support HID keyboards on Surface Laptop 1 and 2 devices.
30 This driver provides support for the HID transport protocol provided
42 select HID
|
| /linux-6.6.21/drivers/iio/common/hid-sensors/ |
| D | Kconfig | 8 tristate "Common modules for all HID Sensor IIO drivers"
12 Say yes here to build support for HID sensor to use
13 HID sensor common processing for attributes and IIO triggers.
15 HID sensor drivers, this module contains processing for those
19 tristate "Common module (trigger) for all HID Sensor IIO drivers"
24 Say yes here to build trigger support for HID sensors.
|
| /linux-6.6.21/drivers/hid/ |
| D | Kconfig | 3 # HID driver configuration
6 bool "HID bus support"
10 This option adds core support for human interface device (HID).
15 config HID config
16 tristate "HID bus core support"
20 A human interface device (HID) is a type of computer device that
21 interacts directly with and takes input from humans. The term "HID"
22 most commonly used to refer to the USB-HID specification, but other
24 designed using HID specification (this involves certain keyboards,
25 mice, tablets, etc). This option adds the HID bus to the kernel,
[all …]
|
| /linux-6.6.21/drivers/hid/usbhid/ |
| D | Kconfig | 2 menu "USB HID support"
6 tristate "USB HID transport layer"
9 select HID
12 mice, joysticks, graphic tablets, or any other HID based devices
25 comment "Input core support is needed for USB HID input layer or HIDBP support"
36 bool "/dev/hiddev raw HID device support"
39 Say Y here if you want to support HID devices (from the USB
48 menu "USB HID Boot Protocol drivers"
56 to use the generic HID driver for your USB keyboard and prefer
72 to use the generic HID driver for your USB mouse and prefer
|
| /linux-6.6.21/Documentation/ABI/testing/ |
| D | configfs-usb-gadget-hid | 8 protocol HID protocol to use
9 report_desc blob corresponding to HID report descriptors
11 report_length HID report length
12 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).
|
| /linux-6.6.21/drivers/hid/bpf/ |
| D | Kconfig | 2 menu "HID-BPF support"
5 bool "HID-BPF support"
10 This option allows to support eBPF programs on the HID subsystem.
11 eBPF programs can fix HID devices in a lighter way than a full
|
| /linux-6.6.21/drivers/iio/orientation/ |
| D | Kconfig | 14 tristate "HID Inclinometer 3D"
16 Say yes here to build support for the HID SENSOR
24 tristate "HID Device Rotation"
26 Say yes here to build support for the HID SENSOR
|
| /linux-6.6.21/drivers/hid/i2c-hid/ |
| D | Kconfig | 3 tristate "I2C HID support"
5 depends on I2C && INPUT && HID
10 tristate "HID over I2C transport layer ACPI driver"
16 other HID based devices which is connected to your computer via I2C.
26 tristate "HID over I2C transport layer Open Firmware driver"
33 other HID based devices which is connected to your computer via I2C.
|
| /linux-6.6.21/Documentation/usb/ |
| D | gadget_hid.rst | 2 Linux USB HID gadget driver
8 The HID Gadget driver provides emulation of USB Human Interface
9 Devices (HID). The basic HID handling is done in the kernel,
10 and HID reports can be sent/received through I/O on the
13 For more details about HID, see the developer page on
21 HID function descriptors you want to use - E.G. something
77 You can add as many HID functions as you want, only limited by
84 some data to the kernel, if HID is a part of a gadget composed with
88 Send and receive HID reports
91 HID reports can be sent/received using read/write on the
[all …]
|
| /linux-6.6.21/Documentation/driver-api/surface_aggregator/ |
| D | overview.rst | 27 and 2 it is required for keyboard HID input. This HID subsystem has been
29 Laptop 3 and Surface Book 3, is responsible for all major HID input (i.e.
50 communicate via HID, specifically using a HID-over-I2C device, whereas on
55 SAM-over-SSH and SAM-over-HID.
58 interface is described in more detail below. The HID interface has not been
|
| /linux-6.6.21/net/bluetooth/hidp/ |
| D | Kconfig | 5 select HID
8 for HID reports. HIDP is required for the Bluetooth Human
|
| /linux-6.6.21/Documentation/devicetree/bindings/input/ |
| D | hid-over-i2c.yaml | 7 title: HID over I2C Devices
14 HID over I2C provides support for various Human Interface Devices over the
44 description: HID descriptor address
|
| /linux-6.6.21/drivers/hid/amd-sfh-hid/ |
| D | Kconfig | 2 menu "AMD SFH HID Support"
8 depends on HID
|
| /linux-6.6.21/drivers/iio/position/ |
| D | Kconfig | 25 tristate "HID Hinge"
29 Say yes here to build support for the HID custom
|