drivers/char/xillybus/xillybus_class.h

File Facts

System

Linux kernel

Corpus path

drivers/char/xillybus/xillybus_class.h

Extension

.h

Size

736 bytes

Lines

31

Domain

Driver Families

Bucket

drivers/char

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/types.h
• linux/device.h
• linux/fs.h
• linux/module.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

const struct file_operations *fops,
			 struct module *owner,
			 void *private_data,
			 unsigned char *idt, unsigned int len,
			 int num_nodes,
			 const char *prefix, bool enumerate);

void xillybus_cleanup_chrdev(void *private_data,
			     struct device *dev);

int xillybus_find_inode(struct inode *inode,
			void **private_data, int *index);

#endif /* __XILLYBUS_CLASS_H */

Annotation

• Immediate include surface: `linux/types.h`, `linux/device.h`, `linux/fs.h`, `linux/module.h`.
• Atlas domain: Driver Families / drivers/char.
• 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.