sound/usb/6fire/common.h
Source file repositories/reference/linux-study-clean/sound/usb/6fire/common.h
File Facts
- System
- Linux kernel
- Corpus path
sound/usb/6fire/common.h- Extension
.h- Size
- 500 bytes
- Lines
- 26
- Domain
- Driver Families
- Bucket
- sound/usb
- Inferred role
- Driver Families: implementation source
- Status
- source 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 or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/slab.hlinux/usb.hsound/core.h
Detected Declarations
struct sfire_chipstruct midi_runtimestruct pcm_runtimestruct control_runtimestruct comm_runtime
Annotated Snippet
#ifndef USB6FIRE_COMMON_H
#define USB6FIRE_COMMON_H
#include <linux/slab.h>
#include <linux/usb.h>
#include <sound/core.h>
#define PREFIX "6fire: "
struct sfire_chip;
struct midi_runtime;
struct pcm_runtime;
struct control_runtime;
struct comm_runtime;
#endif /* USB6FIRE_COMMON_H */
Annotation
- Immediate include surface: `linux/slab.h`, `linux/usb.h`, `sound/core.h`.
- Detected declarations: `struct sfire_chip`, `struct midi_runtime`, `struct pcm_runtime`, `struct control_runtime`, `struct comm_runtime`.
- Atlas domain: Driver Families / sound/usb.
- Implementation status: source 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.