drivers/staging/media/atomisp/pci/runtime/tagger/interface/ia_css_tagger_common.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/runtime/tagger/interface/ia_css_tagger_common.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/runtime/tagger/interface/ia_css_tagger_common.h- Extension
.h- Size
- 827 bytes
- Lines
- 32
- 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.
Dependency Surface
system_local.htype_support.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __IA_CSS_TAGGER_COMMON_H__
#define __IA_CSS_TAGGER_COMMON_H__
#include <system_local.h>
#include <type_support.h>
/**
* @brief The tagger's circular buffer.
*
* Should be one less than NUM_CONTINUOUS_FRAMES in sh_css_internal.h
*/
#define MAX_CB_ELEMS_FOR_TAGGER 14
/**
* @brief Data structure for the tagger buffer element.
*/
typedef struct {
u32 frame; /* the frame value stored in the element */
u32 param; /* the param value stored in the element */
u8 mark; /* the mark on the element */
u8 lock; /* the lock on the element */
u8 exp_id; /* exp_id of frame, for debugging only */
} ia_css_tagger_buf_sp_elem_t;
#endif /* __IA_CSS_TAGGER_COMMON_H__ */
Annotation
- Immediate include surface: `system_local.h`, `type_support.h`.
- 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.