drivers/staging/media/atomisp/pci/hive_isp_css_common/debug_global.h

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/atomisp/pci/hive_isp_css_common/debug_global.h

Extension

.h

Size

1843 bytes

Lines

67

Domain

Driver Families

Bucket

drivers/staging

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

• type_support.h

Detected Declarations

• struct debug_data_s
• struct debug_data_ddr_s

Annotated Snippet

struct debug_data_s {
	u32			enable;
	u32			bufmode;
	u32			head;
	u32			tail;
	u32			buf[DEBUG_BUF_SIZE];
};

/* thread.sp.c doesn't have a notion of HIVE_ISP_DDR_WORD_BYTES
   still one point of control is needed for debug purposes */

#ifdef HIVE_ISP_DDR_WORD_BYTES
struct debug_data_ddr_s {
	u32			enable;
	s8				padding1[HIVE_ISP_DDR_WORD_BYTES - sizeof(uint32_t)];
	u32			bufmode;
	s8				padding2[HIVE_ISP_DDR_WORD_BYTES - sizeof(uint32_t)];
	u32			head;
	s8				padding3[HIVE_ISP_DDR_WORD_BYTES - sizeof(uint32_t)];
	u32			tail;
	s8				padding4[HIVE_ISP_DDR_WORD_BYTES - sizeof(uint32_t)];
	u32			buf[DEBUG_BUF_SIZE];
};
#endif

#endif /* __DEBUG_GLOBAL_H_INCLUDED__ */

Annotation

• Immediate include surface: `type_support.h`.
• Detected declarations: `struct debug_data_s`, `struct debug_data_ddr_s`.
• Atlas domain: Driver Families / drivers/staging.
• 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.