drivers/staging/media/atomisp/pci/sh_css_mipi.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/sh_css_mipi.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/sh_css_mipi.h- Extension
.h- Size
- 577 bytes
- Lines
- 27
- 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_err.hia_css_types.hia_css_stream_public.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __SH_CSS_MIPI_H
#define __SH_CSS_MIPI_H
#include <ia_css_err.h> /* ia_css_err */
#include <ia_css_types.h> /* ia_css_pipe */
#include <ia_css_stream_public.h> /* ia_css_stream_config */
void
mipi_init(void);
int
allocate_mipi_frames(struct ia_css_pipe *pipe, struct ia_css_stream_info *info);
int
free_mipi_frames(struct ia_css_pipe *pipe);
int
send_mipi_frames(struct ia_css_pipe *pipe);
#endif /* __SH_CSS_MIPI_H */
Annotation
- Immediate include surface: `ia_css_err.h`, `ia_css_types.h`, `ia_css_stream_public.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.