drivers/staging/media/atomisp/pci/runtime/bufq/interface/ia_css_bufq_comm.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/runtime/bufq/interface/ia_css_bufq_comm.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/runtime/bufq/interface/ia_css_bufq_comm.h- Extension
.h- Size
- 788 bytes
- Lines
- 33
- 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_global.h
Detected Declarations
enum sh_css_queue_id
Annotated Snippet
#ifndef _IA_CSS_BUFQ_COMM_H
#define _IA_CSS_BUFQ_COMM_H
#include "system_global.h"
enum sh_css_queue_id {
SH_CSS_INVALID_QUEUE_ID = -1,
SH_CSS_QUEUE_A_ID = 0,
SH_CSS_QUEUE_B_ID,
SH_CSS_QUEUE_C_ID,
SH_CSS_QUEUE_D_ID,
SH_CSS_QUEUE_E_ID,
SH_CSS_QUEUE_F_ID,
SH_CSS_QUEUE_G_ID,
SH_CSS_QUEUE_H_ID, /* for metadata */
#define SH_CSS_MAX_NUM_QUEUES (SH_CSS_QUEUE_H_ID + 1)
};
#define SH_CSS_MAX_DYNAMIC_BUFFERS_PER_THREAD SH_CSS_MAX_NUM_QUEUES
/* for now we staticaly assign queue 0 & 1 to parameter sets */
#define IA_CSS_PARAMETER_SET_QUEUE_ID SH_CSS_QUEUE_A_ID
#define IA_CSS_PER_FRAME_PARAMETER_SET_QUEUE_ID SH_CSS_QUEUE_B_ID
#endif
Annotation
- Immediate include surface: `system_global.h`.
- Detected declarations: `enum sh_css_queue_id`.
- 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.