sound/aoa/soundbus/soundbus.h

File Facts

System

Linux kernel

Corpus path

sound/aoa/soundbus/soundbus.h

Extension

.h

Size

6486 bytes

Lines

202

Domain

Driver Families

Bucket

sound/aoa

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/platform_device.h
• sound/pcm.h
• linux/list.h

Detected Declarations

• struct transfer_info
• struct codec_info_item
• struct bus_info
• struct codec_info
• struct soundbus_dev
• struct soundbus_driver
• enum clock_switch

Annotated Snippet

struct device_driver driver;
};
#define to_soundbus_driver(drv) container_of(drv,struct soundbus_driver, driver)

extern int soundbus_register_driver(struct soundbus_driver *drv);
extern void soundbus_unregister_driver(struct soundbus_driver *drv);

extern struct attribute *soundbus_dev_attrs[];

#endif /* __SOUNDBUS_H */

Annotation

• Immediate include surface: `linux/platform_device.h`, `sound/pcm.h`, `linux/list.h`.
• Detected declarations: `struct transfer_info`, `struct codec_info_item`, `struct bus_info`, `struct codec_info`, `struct soundbus_dev`, `struct soundbus_driver`, `enum clock_switch`.
• Atlas domain: Driver Families / sound/aoa.
• 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.