drivers/hwtracing/coresight/coresight-ctcu.h

File Facts

System

Linux kernel

Corpus path

drivers/hwtracing/coresight/coresight-ctcu.h

Extension

.h

Size

917 bytes

Lines

40

Domain

Driver Families

Bucket

drivers/hwtracing

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• coresight-trace-id.h

Detected Declarations

• struct ctcu_etr_config
• struct ctcu_config
• struct ctcu_drvdata

Annotated Snippet

struct ctcu_etr_config {
	const u32 atid_offset;
	const u32 port_num;
};

struct ctcu_config {
	const struct ctcu_etr_config *etr_cfgs;
	int num_etr_config;
};

struct ctcu_drvdata {
	void __iomem		*base;
	struct clk		*apb_clk;
	struct device		*dev;
	struct coresight_device	*csdev;
	raw_spinlock_t		spin_lock;
	u32			atid_offset[ETR_MAX_NUM];
	/* refcnt for each traceid of each sink */
	u8			traceid_refcnt[ETR_MAX_NUM][CORESIGHT_TRACE_ID_RES_TOP];
};

#endif

Annotation

• Immediate include surface: `coresight-trace-id.h`.
• Detected declarations: `struct ctcu_etr_config`, `struct ctcu_config`, `struct ctcu_drvdata`.
• Atlas domain: Driver Families / drivers/hwtracing.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.