include/linux/platform_data/asoc-ti-mcbsp.h

File Facts

System

Linux kernel

Corpus path

include/linux/platform_data/asoc-ti-mcbsp.h

Extension

.h

Size

820 bytes

Lines

35

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/spinlock.h
• linux/clk.h

Detected Declarations

• struct omap_mcbsp_ops
• struct omap_mcbsp_platform_data

Annotated Snippet

struct omap_mcbsp_ops {
	void (*request)(unsigned int);
	void (*free)(unsigned int);
};

struct omap_mcbsp_platform_data {
	struct omap_mcbsp_ops *ops;
	u16 buffer_size;
	u8 reg_size;
	u8 reg_step;

	/* McBSP platform and instance specific features */
	bool has_wakeup; /* Wakeup capability */
	bool has_ccr; /* Transceiver has configuration control registers */
	int (*force_ick_on)(struct clk *clk, bool force_on);
};

void omap3_mcbsp_init_pdata_callback(struct omap_mcbsp_platform_data *pdata);

#endif

Annotation

• Immediate include surface: `linux/spinlock.h`, `linux/clk.h`.
• Detected declarations: `struct omap_mcbsp_ops`, `struct omap_mcbsp_platform_data`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.