drivers/s390/cio/crw.c

File Facts

System

Linux kernel

Corpus path

drivers/s390/cio/crw.c

Extension

.c

Size

4102 bytes

Lines

162

Domain

Driver Families

Bucket

drivers/s390

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/mutex.h
• linux/kthread.h
• linux/init.h
• linux/wait.h
• asm/ctlreg.h
• asm/crw.h
• ioasm.h

Detected Declarations

• function crw_register_handler
• function crw_unregister_handler
• function crw_collect_info
• function crw_handle_channel_report
• function crw_wait_for_channel_report
• function crw_machine_check_init
• module init crw_machine_check_init

Annotated Snippet

device_initcall(crw_machine_check_init);

Annotation

• Immediate include surface: `linux/mutex.h`, `linux/kthread.h`, `linux/init.h`, `linux/wait.h`, `asm/ctlreg.h`, `asm/crw.h`, `ioasm.h`.
• Detected declarations: `function crw_register_handler`, `function crw_unregister_handler`, `function crw_collect_info`, `function crw_handle_channel_report`, `function crw_wait_for_channel_report`, `function crw_machine_check_init`, `module init crw_machine_check_init`.
• Atlas domain: Driver Families / drivers/s390.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.