drivers/staging/media/atomisp/pci/runtime/spctrl/interface/ia_css_spctrl_comm.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/runtime/spctrl/interface/ia_css_spctrl_comm.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/runtime/spctrl/interface/ia_css_spctrl_comm.h- Extension
.h- Size
- 1219 bytes
- Lines
- 42
- 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
linux/build_bug.htype_support.h
Detected Declarations
struct ia_css_sp_init_dmem_cfg
Annotated Snippet
struct ia_css_sp_init_dmem_cfg {
ia_css_ptr ddr_data_addr; /** data segment address in ddr */
u32 dmem_data_addr; /** data segment address in dmem */
u32 dmem_bss_addr; /** bss segment address in dmem */
u32 data_size; /** data segment size */
u32 bss_size; /** bss segment size */
sp_ID_t sp_id; /* <sp Id */
};
#define SIZE_OF_IA_CSS_SP_INIT_DMEM_CFG_STRUCT \
(1 * SIZE_OF_IA_CSS_PTR) + \
(4 * sizeof(uint32_t)) + \
(1 * sizeof(sp_ID_t))
static_assert(sizeof(struct ia_css_sp_init_dmem_cfg) == SIZE_OF_IA_CSS_SP_INIT_DMEM_CFG_STRUCT);
#endif /* __IA_CSS_SPCTRL_COMM_H__ */
Annotation
- Immediate include surface: `linux/build_bug.h`, `type_support.h`.
- Detected declarations: `struct ia_css_sp_init_dmem_cfg`.
- 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.