drivers/media/rc/ir-sanyo-decoder.c

File Facts

System

Linux kernel

Corpus path

drivers/media/rc/ir-sanyo-decoder.c

Extension

.c

Size

6113 bytes

Lines

236

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

• linux/module.h
• linux/bitrev.h
• rc-core-priv.h

Detected Declarations

• enum sanyo_state
• function ir_sanyo_decode
• function ir_sanyo_encode
• function ir_sanyo_decode_init
• function ir_sanyo_decode_exit
• module init ir_sanyo_decode_init

Annotated Snippet

module_init(ir_sanyo_decode_init);
module_exit(ir_sanyo_decode_exit);

MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Mauro Carvalho Chehab");
MODULE_AUTHOR("Red Hat Inc. (http://www.redhat.com)");
MODULE_DESCRIPTION("SANYO IR protocol decoder");

Annotation

• Immediate include surface: `linux/module.h`, `linux/bitrev.h`, `rc-core-priv.h`.
• Detected declarations: `enum sanyo_state`, `function ir_sanyo_decode`, `function ir_sanyo_encode`, `function ir_sanyo_decode_init`, `function ir_sanyo_decode_exit`, `module init ir_sanyo_decode_init`.
• 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.