hid (full) in projects: Documentation - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:hid (Results 1 – 25 of 70) sorted by relevance

12 3

/Documentation/hid/
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	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	index.rst	`4 Human Interface Devices (HID) 13 hid-sensor 14 hid-transport 15 hid-bpf 19 hid-alps 20 intel-ish-hid 21 amd-sfh-hid`
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 9 With UHID, a user-space transport driver can create kernel hid-devices for each 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 [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	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 24 usb.c ---> hid-core.c ----> hid-input.c ----> [keyboard/mouse/joystick/event] 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 [all …]
D	hidreport-parsing.rst	4 Manual parsing of HID report descriptors 7 Consider again the mouse HID report descriptor 8 introduced in Documentation/hid/hidintro.rst:: 10 $ hexdump -C /sys/bus/hid/devices/0003\:093A\:2510.0002/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
/Documentation/devicetree/bindings/input/
D	hid-over-i2c.yaml	4 $id: http://devicetree.org/schemas/input/hid-over-i2c.yaml# 7 title: HID over I2C Devices 14 HID over I2C provides support for various Human Interface Devices over the 21 If this binding is used, the kernel module i2c-hid will handle the communication 22 with the device and the generic hid core layer will handle the protocol. 33 - const: hid-over-i2c 34 - description: Just "hid-over-i2c" alone is allowed, but not recommended. 35 const: hid-over-i2c 43 hid-descr-addr: 44 description: HID descriptor address [all …]
/Documentation/ABI/testing/
D	sysfs-driver-hid-ntrig	1 What: /sys/bus/hid/drivers/ntrig/<dev>/activate_slack 10 What: /sys/bus/hid/drivers/ntrig/<dev>/decativate_slack 24 What: /sys/bus/hid/drivers/ntrig/<dev>/activation_width 25 What: /sys/bus/hid/drivers/ntrig/<dev>/activation_height 40 What: /sys/bus/hid/drivers/ntrig/<dev>/min_width 41 What: /sys/bus/hid/drivers/ntrig/<dev>/min_height 57 What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_physical_width 58 What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_physical_height 67 What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_logical_width 68 What: /sys/bus/hid/drivers/ntrig/<dev>/sensor_logical_height
D	configfs-usb-gadget-hid	`1 What: /config/usb-gadget/gadget/functions/hid.name 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	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 2 What: /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/report_descriptor 7 Description: When read, this file returns the device's raw binary HID 12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 13 What: /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/country 19 of the device's HID country code (e.g. 21 for US).
D	sysfs-driver-wacom	1 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed 6 The /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed file 12 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/led 23 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status0_luminance 33 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status1_luminance 42 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status_led0_select 52 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status_led1_select 61 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/buttons_luminance 68 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/button<n>_rawimg 87 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_remote/unpair_remote [all …]
D	sysfs-driver-hid-wiimote	`1 What: /sys/bus/hid/drivers/wiimote/<dev>/led1 2 What: /sys/bus/hid/drivers/wiimote/<dev>/led2 3 What: /sys/bus/hid/drivers/wiimote/<dev>/led3 4 What: /sys/bus/hid/drivers/wiimote/<dev>/led4 12 What: /sys/bus/hid/drivers/wiimote/<dev>/extension 29 What: /sys/bus/hid/drivers/wiimote/<dev>/devtype 51 What: /sys/bus/hid/drivers/wiimote/<dev>/bboard_calib 67 What: /sys/bus/hid/drivers/wiimote/<dev>/pro_calib`
D	sysfs-driver-hid-lenovo	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 11 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 20 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 27 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 37 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 44 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 53 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
D	sysfs-driver-hid-logitech-hidpp	`1 What: /sys/bus/hid/drivers/logitech-hidpp-device/<dev>/range 11 What: /sys/bus/hid/drivers/logitech-hidpp-device/<dev>/builtin_power_supply 16 Presence of this file indicates that HID++ driver is capable of`
D	sysfs-driver-hid-picolcd	`1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 13 Note: when switching mode the current PicoLCD HID device gets 18 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 28 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…`
/Documentation/usb/
D	functionfs.rst	`46 One can imagine a gadget that has an Ethernet, MTP and HID interfaces 50 $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid 53 $ mkdir /dev/ffs-hid && mount -t functionfs hid /dev/ffs-hid 54 $ ( cd /dev/ffs-hid && hid-daemon ) & 57 whether its FunctionFS is designed for MTP ("mtp") or HID ("hid").`
/Documentation/ABI/obsolete/
D	sysfs-driver-hid-roccat-ryos	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 9 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 61 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 81 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 92 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… [all …]
D	sysfs-driver-hid-roccat-isku	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 20 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 61 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 81 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 91 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… [all …]
D	sysfs-driver-hid-roccat-konepure	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 13 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 29 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 40 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 55 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 71 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 80 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 88 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 97 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
D	sysfs-driver-hid-roccat-koneplus	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 24 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 36 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 44 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 55 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 70 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 82 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 98 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 111 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… [all …]
D	sysfs-driver-hid-roccat-kovaplus	1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 11 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 22 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 32 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 42 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 54 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 62 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 77 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 89 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p… 105 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
/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`

12 3

Documentation
LICENSES
arch
block
certs
crypto
drivers
fs
gki
include
init
io_uring
ipc
kernel
lib
mm
net
rust
samples
scripts
security
sound
tools
usr
virt