drivers/input/misc/xen-kbdfront.c

File Facts

System

Linux kernel

Corpus path

drivers/input/misc/xen-kbdfront.c

Extension

.c

Size

14261 bytes

Lines

573

Domain

Driver Families

Bucket

drivers/input

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/errno.h
• linux/module.h
• linux/input.h
• linux/input/mt.h
• linux/slab.h
• asm/xen/hypervisor.h
• xen/xen.h
• xen/events.h
• xen/page.h
• xen/grant_table.h
• xen/interface/grant_table.h
• xen/interface/io/fbif.h
• xen/interface/io/kbdif.h
• xen/xenbus.h
• xen/platform_pci.h

Detected Declarations

• struct xenkbd_info
• function xenkbd_handle_motion_event
• function xenkbd_handle_position_event
• function xenkbd_handle_key_event
• function xenkbd_handle_mt_event
• function xenkbd_handle_event
• function input_handler
• function xenkbd_probe
• function xenkbd_resume
• function xenkbd_remove
• function xenkbd_connect_backend
• function xenkbd_disconnect_backend
• function xenkbd_backend_changed
• function xenkbd_init
• function xenkbd_cleanup
• module init xenkbd_init

Annotated Snippet

module_init(xenkbd_init);
module_exit(xenkbd_cleanup);

MODULE_DESCRIPTION("Xen virtual keyboard/pointer device frontend");
MODULE_LICENSE("GPL");
MODULE_ALIAS("xen:" XENKBD_DRIVER_NAME);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/errno.h`, `linux/module.h`, `linux/input.h`, `linux/input/mt.h`, `linux/slab.h`, `asm/xen/hypervisor.h`, `xen/xen.h`.
• Detected declarations: `struct xenkbd_info`, `function xenkbd_handle_motion_event`, `function xenkbd_handle_position_event`, `function xenkbd_handle_key_event`, `function xenkbd_handle_mt_event`, `function xenkbd_handle_event`, `function input_handler`, `function xenkbd_probe`, `function xenkbd_resume`, `function xenkbd_remove`.
• Atlas domain: Driver Families / drivers/input.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.