sound/firewire/cmp.h

File Facts

System

Linux kernel

Corpus path

sound/firewire/cmp.h

Extension

.h

Size

1491 bytes

Lines

53

Domain

Driver Families

Bucket

sound/firewire

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/mutex.h
• linux/types.h
• iso-resources.h

Detected Declarations

• struct fw_unit
• struct cmp_connection
• enum cmp_direction

Annotated Snippet

struct cmp_connection {
	int speed;
	/* private: */
	bool connected;
	struct mutex mutex;
	struct fw_iso_resources resources;
	__be32 last_pcr_value;
	unsigned int pcr_index;
	unsigned int max_speed;
	enum cmp_direction direction;
};

int cmp_connection_init(struct cmp_connection *connection,
			struct fw_unit *unit,
			enum cmp_direction direction,
			unsigned int pcr_index);
int cmp_connection_check_used(struct cmp_connection *connection, bool *used);
void cmp_connection_destroy(struct cmp_connection *connection);

int cmp_connection_reserve(struct cmp_connection *connection,
			   unsigned int max_payload);
void cmp_connection_release(struct cmp_connection *connection);

int cmp_connection_establish(struct cmp_connection *connection);
void cmp_connection_break(struct cmp_connection *connection);

#endif

Annotation

• Immediate include surface: `linux/mutex.h`, `linux/types.h`, `iso-resources.h`.
• Detected declarations: `struct fw_unit`, `struct cmp_connection`, `enum cmp_direction`.
• Atlas domain: Driver Families / sound/firewire.
• 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.