drivers/staging/media/atomisp/pci/atomisp_common.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/atomisp_common.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/atomisp_common.h- Extension
.h- Size
- 1252 bytes
- Lines
- 60
- 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
../../include/linux/atomisp.hlinux/v4l2-mediabus.hmedia/videobuf2-v4l2.hatomisp_compat.hia_css.h
Detected Declarations
struct atomisp_format_bridgestruct atomisp_fmt
Annotated Snippet
struct atomisp_format_bridge {
unsigned int pixelformat;
unsigned int depth;
u32 mbus_code;
enum ia_css_frame_format sh_fmt;
unsigned char description[32]; /* the same as struct v4l2_fmtdesc */
bool planar;
};
struct atomisp_fmt {
u32 pixelformat;
u32 depth;
u32 bytesperline;
u32 framesize;
u32 imagesize;
u32 width;
u32 height;
u32 bayer_order;
};
#endif
Annotation
- Immediate include surface: `../../include/linux/atomisp.h`, `linux/v4l2-mediabus.h`, `media/videobuf2-v4l2.h`, `atomisp_compat.h`, `ia_css.h`.
- Detected declarations: `struct atomisp_format_bridge`, `struct atomisp_fmt`.
- 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.