Lines Matching refs:report
41 Simple fixup of report descriptor
45 in the report descriptor. These fixes all require a kernel patch and the
117 Thus, all of the parsing of the HID report and the HID report descriptor
142 3. change of the report descriptor with ``SEC("fmod_ret/hid_bpf_rdesc_fixup")`` in libbpf
154 change the report descriptor from the BPF program. Once a ``hid_bpf_rdesc_fixup``
198 1. for a given device, if we know that the report length will always be of a certain value,
199 we can request the ``data`` pointer to point at the full report length.
212 2. if the report length is variable, but we know the value of ``X`` is always a 16-bit
274 content of the report descriptor. The memory associated with that buffer is
278 modified content and size as the report descriptor.
289 Thus, if we need to replace a report descriptor fixup, some cooperation is
290 required from the owner of the original report descriptor fixup.
314 even if we change its report descriptor.
317 accessing the current report descriptor of the device through the sysfs.
321 Parsing the report descriptor is the responsibility of the BPF programmer or the userspace
333 physical position of the switch through a feature report.
346 one byte in the report is less than ideal.
450 needs to emit a feature report on the device itself.
506 args.data[0] = 0x02; /* report ID of the feature on our device */