drivers/w1/w1_internal.h

File Facts

System

Linux kernel

Corpus path

drivers/w1/w1_internal.h

Extension

.h

Size

2694 bytes

Lines

79

Domain

Driver Families

Bucket

drivers/w1

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/w1.h
• linux/completion.h
• linux/mutex.h

Detected Declarations

• struct w1_async_cmd

Annotated Snippet

extern struct device_driver w1_master_driver;
extern struct device w1_master_device;
extern int w1_max_slave_count;
extern int w1_max_slave_ttl;
extern struct list_head w1_masters;
extern struct mutex w1_mlock;
extern spinlock_t w1_flock;

int w1_process_callbacks(struct w1_master *dev);
int w1_process(void *data);

#endif /* __W1_H */

Annotation

• Immediate include surface: `linux/w1.h`, `linux/completion.h`, `linux/mutex.h`.
• Detected declarations: `struct w1_async_cmd`.
• Atlas domain: Driver Families / drivers/w1.
• 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.