drivers/staging/media/atomisp/pci/runtime/ifmtr/interface/ia_css_ifmtr.h

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/atomisp/pci/runtime/ifmtr/interface/ia_css_ifmtr.h

Extension

.h

Size

688 bytes

Lines

26

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

• type_support.h
• ia_css_stream_public.h
• ia_css_binary.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __IA_CSS_IFMTR_H__
#define __IA_CSS_IFMTR_H__

#include <type_support.h>
#include <ia_css_stream_public.h>
#include <ia_css_binary.h>

extern bool ifmtr_set_if_blocking_mode_reset;

unsigned int ia_css_ifmtr_lines_needed_for_bayer_order(
    const struct ia_css_stream_config *config);

unsigned int ia_css_ifmtr_columns_needed_for_bayer_order(
    const struct ia_css_stream_config *config);

int ia_css_ifmtr_configure(struct ia_css_stream_config *config,
				       struct ia_css_binary *binary);

#endif /* __IA_CSS_IFMTR_H__ */

Annotation

• Immediate include surface: `type_support.h`, `ia_css_stream_public.h`, `ia_css_binary.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.