Home
last modified time | relevance | path

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

/linux/tools/testing/selftests/hid/
H A Dhidraw.c14 FIXTURE(hidraw) { in FIXTURE()
18 static void close_hidraw(FIXTURE_DATA(hidraw) * self) in close_hidraw()
25 FIXTURE_TEARDOWN(hidraw) { in FIXTURE_TEARDOWN()
38 FIXTURE_SETUP(hidraw) in FIXTURE_SETUP()
53 TEST_F(hidraw, test_create_uhid)
59 * check that we get the same data through hidraw in TEST_F()
61 TEST_F(hidraw, raw_event) in TEST_F()
71 /* read the data from hidraw */ in TEST_F()
80 * After initial opening/checks of hidraw, revoke the hidraw in TEST_F() argument
11 FIXTURE(hidraw) FIXTURE() argument
22 FIXTURE_TEARDOWN(hidraw) FIXTURE_TEARDOWN() argument
35 FIXTURE_SETUP(hidraw) FIXTURE_SETUP() argument
50 TEST_F(hidraw,test_create_uhid) TEST_F() argument
58 TEST_F(hidraw,raw_event) TEST_F() argument
117 TEST_F(hidraw,ioctl_revoked) TEST_F() argument
135 TEST_F(hidraw,poll_revoked) TEST_F() argument
176 TEST_F(hidraw,write_event_revoked) TEST_F() argument
[all...]
H A DMakefile38 TEST_GEN_PROGS = hid_bpf hidraw
/linux/Documentation/ABI/testing/
H A Dsysfs-driver-hid3 What: /sys/class/hidraw/hidraw<num>/device/report_descriptor
14 What: /sys/class/hidraw/hidraw<num>/device/country
/linux/include/linux/
H A Dhidraw.h11 struct hidraw { struct
32 struct hidraw *hidraw; argument
H A Dhid.h696 void *hidraw; member
/linux/Documentation/hid/
H 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.
H 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
275 processed by the HID stack. Clients (hidraw, input, LEDs) will **not** see this event.
330 We can not rely on hidraw to bind a BPF program to a HID device. hidraw is an
333 (where it is interesting to get the non-hidraw traces).
338 Given that hidraw is not stable when the device disconnects/reconnects, we recommend
364 position is actually reported in the flow of the pen events, using hidraw to implement
457 Instead of using hidraw for that, we can create a ``SEC("syscall")`` program
H A Dhidintro.rst81 directly accessing the hidraw driver [#hidraw]_.
509 .. [#hidraw] read hidraw: see Documentation/hid/hidraw.rst and
510 file `samples/hidraw/hid-example.c` for an example.
/linux/Documentation/hwmon/
H 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/samples/
H A DMakefile11 subdir-$(CONFIG_SAMPLE_HIDRAW) += hidraw
H A DKconfig162 bool "hidraw sample"
/linux/drivers/hid/
H A Dhid-u2fzero.c348 minor = ((struct hidraw *) hdev->hidraw)->minor; in u2fzero_probe()
H A Dhid-led.c491 minor = ((struct hidraw *) hdev->hidraw)->minor; in hidled_probe()
H A Dhid-cp2112.c1294 ((struct hidraw *)hdev->hidraw)->minor); in cp2112_probe()
H 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.
/linux/Documentation/userspace-api/ioctl/
H A Dioctl-number.rst149 'H' 00-0F linux/hidraw.h conflict!