Home
last modified time | relevance | path

Searched refs:hidraw (Results 1 – 17 of 17) sorted by relevance

/linux-6.3-rc2/drivers/hid/
A Dhidraw.c265 struct hidraw *dev; in hidraw_open()
319 static void drop_ref(struct hidraw *hidraw, int exists_bit) in drop_ref() argument
322 hidraw->exist = 0; in drop_ref()
323 if (hidraw->open) { in drop_ref()
330 --hidraw->open; in drop_ref()
335 kfree(hidraw); in drop_ref()
371 struct hidraw *dev; in hidraw_ioctl()
511 struct hidraw *dev = hid->hidraw; in hidraw_report_event()
541 struct hidraw *dev; in hidraw_connect()
586 hid->hidraw = dev; in hidraw_connect()
[all …]
A Dhid-u2fzero.c348 minor = ((struct hidraw *) hdev->hidraw)->minor; in u2fzero_probe()
A Dhid-led.c491 minor = ((struct hidraw *) hdev->hidraw)->minor; in hidled_probe()
A DMakefile15 hid-$(CONFIG_HIDRAW) += hidraw.o
A Dhid-cp2112.c1315 ((struct hidraw *)hdev->hidraw)->minor); in cp2112_probe()
A DKconfig46 bool "/dev/hidraw raw HID device support"
53 event interface on /dev/hidraw.
74 special HID-drivers. You should use hidraw for that.
A Dhid-core.c2222 ((struct hidraw *)hdev->hidraw)->minor); in hid_connect()
/linux-6.3-rc2/include/linux/
A Dhidraw.h11 struct hidraw { struct
32 struct hidraw *hidraw; argument
A Dhid.h630 void *hidraw; member
/linux-6.3-rc2/Documentation/ABI/testing/
A Dsysfs-driver-hid3 What: /sys/class/hidraw/hidraw<num>/device/report_descriptor
14 What: /sys/class/hidraw/hidraw<num>/device/country
/linux-6.3-rc2/Documentation/hid/
A Dhidraw.rst5 The hidraw driver provides a raw interface to USB and Bluetooth Human
23 A benefit of hidraw is that its use by userspace applications is independent
24 of the underlying hardware type. Currently, hidraw is implemented for USB
26 use the HID specification, hidraw will be expanded to add support for these
30 create hidraw device nodes. Udev will typically create the device nodes
32 and udev rule-dependent, applications should use libudev to locate hidraw
174 and all the ioctls for hidraw. The code may be used by anyone for any
176 hidraw.
A Dindex.rst11 hidraw
A Dhid-bpf.rst62 Instead of using hidraw or creating new sysfs entries or ioctls, we can rely
104 Right now, tracing relies on hidraw. It works well except for a couple
107 1. if the driver doesn't export a hidraw node, we can't trace anything
109 2. hidraw doesn't catch other processes' requests to the device, which
251 processed by the HID stack. Clients (hidraw, input, LEDs) will **not** see this event.
308 We can not rely on hidraw to bind a BPF program to a HID device. hidraw is an
311 (where it is interesting to get the non-hidraw traces).
316 Given that hidraw is not stable when the device disconnects/reconnects, we recommend
342 position is actually reported in the flow of the pen events, using hidraw to implement
452 Instead of using hidraw for that, we can create a ``SEC("syscall")`` program
/linux-6.3-rc2/Documentation/hwmon/
A Dnzxt-smart2.rst35 `liquidctl`_) can be used to run "detect fans" command through hidraw interface.
37 The driver coexists with userspace tools that access the device through hidraw
/linux-6.3-rc2/samples/
A DMakefile9 subdir-$(CONFIG_SAMPLE_HIDRAW) += hidraw
A DKconfig162 bool "hidraw sample"
/linux-6.3-rc2/Documentation/userspace-api/ioctl/
A Dioctl-number.rst141 'H' 00-0F linux/hidraw.h conflict!

Completed in 27 milliseconds