drivers/input/input-poller.h
Source file repositories/reference/linux-study-clean/drivers/input/input-poller.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/input/input-poller.h- Extension
.h- Size
- 478 bytes
- Lines
- 19
- Domain
- Driver Families
- Bucket
- drivers/input
- 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
linux/sysfs.h
Detected Declarations
struct input_dev_poller
Annotated Snippet
#ifndef _INPUT_POLLER_H
#define _INPUT_POLLER_H
/*
* Support for polling mode for input devices.
*/
#include <linux/sysfs.h>
struct input_dev_poller;
void input_dev_poller_finalize(struct input_dev_poller *poller);
void input_dev_poller_start(struct input_dev_poller *poller);
void input_dev_poller_stop(struct input_dev_poller *poller);
extern struct attribute_group input_poller_attribute_group;
#endif /* _INPUT_POLLER_H */
Annotation
- Immediate include surface: `linux/sysfs.h`.
- Detected declarations: `struct input_dev_poller`.
- Atlas domain: Driver Families / drivers/input.
- 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.