drivers/s390/char/tape_class.h

File Facts

System

Linux kernel

Corpus path

drivers/s390/char/tape_class.h

Extension

.h

Size

1662 bytes

Lines

62

Domain

Driver Families

Bucket

drivers/s390

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/module.h
• linux/fs.h
• linux/major.h
• linux/cdev.h
• linux/device.h
• linux/kdev_t.h

Detected Declarations

• struct tape_class_device

Annotated Snippet

const struct file_operations *fops,
	char *			device_name,
	char *			node_name
);
void unregister_tape_dev(struct device *device, struct tape_class_device *tcd);
int tape_class_init(void);
void tape_class_exit(void);

#endif /* __TAPE_CLASS_H__ */

Annotation

• Immediate include surface: `linux/init.h`, `linux/module.h`, `linux/fs.h`, `linux/major.h`, `linux/cdev.h`, `linux/device.h`, `linux/kdev_t.h`.
• Detected declarations: `struct tape_class_device`.
• Atlas domain: Driver Families / drivers/s390.
• Implementation status: pattern 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.