drivers/staging/media/atomisp/pci/isp/kernels/ref/ref_1.0/ia_css_ref.host.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/isp/kernels/ref/ref_1.0/ia_css_ref.host.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/isp/kernels/ref/ref_1.0/ia_css_ref.host.h- Extension
.h- Size
- 802 bytes
- Lines
- 30
- 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
ia_css_frame_public.hia_css_binary.hia_css_ref_types.hia_css_ref_param.hia_css_ref_state.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __IA_CSS_REF_HOST_H
#define __IA_CSS_REF_HOST_H
#include <ia_css_frame_public.h>
#include <ia_css_binary.h>
#include "ia_css_ref_types.h"
#include "ia_css_ref_param.h"
#include "ia_css_ref_state.h"
int ia_css_ref_config(struct sh_css_isp_ref_isp_config *to,
const struct ia_css_ref_configuration *from,
unsigned int size);
int ia_css_ref_configure(const struct ia_css_binary *binary,
const struct ia_css_frame * const *ref_frames,
const uint32_t dvs_frame_delay);
void
ia_css_init_ref_state(
struct sh_css_isp_ref_dmem_state *state,
unsigned int size);
#endif /* __IA_CSS_REF_HOST_H */
Annotation
- Immediate include surface: `ia_css_frame_public.h`, `ia_css_binary.h`, `ia_css_ref_types.h`, `ia_css_ref_param.h`, `ia_css_ref_state.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.