drivers/media/rc/keymaps/rc-avermedia-m135a.c

File Facts

System

Linux kernel

Corpus path

drivers/media/rc/keymaps/rc-avermedia-m135a.c

Extension

.c

Size

3758 bytes

Lines

146

Domain

Driver Families

Bucket

drivers/media

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• media/rc-map.h
• linux/module.h

Detected Declarations

• function init_rc_map_avermedia_m135a
• function exit_rc_map_avermedia_m135a
• module init init_rc_map_avermedia_m135a

Annotated Snippet

module_init(init_rc_map_avermedia_m135a)
module_exit(exit_rc_map_avermedia_m135a)

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Mauro Carvalho Chehab");
MODULE_DESCRIPTION("Avermedia M135A with RM-JX and RM-K6 remote controller keytable");

Annotation

• Immediate include surface: `media/rc-map.h`, `linux/module.h`.
• Detected declarations: `function init_rc_map_avermedia_m135a`, `function exit_rc_map_avermedia_m135a`, `module init init_rc_map_avermedia_m135a`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: integration 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.