drivers/hid/bpf/progs/XPPen__ACK05.bpf.c

File Facts

System

Linux kernel

Corpus path

drivers/hid/bpf/progs/XPPen__ACK05.bpf.c

Extension

.c

Size

11885 bytes

Lines

332

Domain

Driver Families

Bucket

drivers/hid

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• vmlinux.h
• hid_bpf.h
• hid_bpf_helpers.h
• hid_report_helpers.h
• bpf/bpf_tracing.h
• hid_bpf_async.h

Detected Declarations

• function BPF_PROG
• function HID_BPF_ASYNC_FUN
• function BPF_PROG
• function probe

Annotated Snippet

if (!hctx) {
			ctx->retval = -EINVAL;
			return 0;
		}

		ctx->retval = HID_BPF_ASYNC_INIT(switch_to_raw_mode) ||
			      switch_to_raw_mode(hctx);

		hid_bpf_release_context(hctx);
	}

	return 0;
}

char _license[] SEC("license") = "GPL";

Annotation

• Immediate include surface: `vmlinux.h`, `hid_bpf.h`, `hid_bpf_helpers.h`, `hid_report_helpers.h`, `bpf/bpf_tracing.h`, `hid_bpf_async.h`.
• Detected declarations: `function BPF_PROG`, `function HID_BPF_ASYNC_FUN`, `function BPF_PROG`, `function probe`.
• Atlas domain: Driver Families / drivers/hid.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.