drivers/staging/media/atomisp/pci/isp/kernels/bnr/bnr2_2/ia_css_bnr2_2.host.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/isp/kernels/bnr/bnr2_2/ia_css_bnr2_2.host.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/isp/kernels/bnr/bnr2_2/ia_css_bnr2_2.host.h- Extension
.h- Size
- 639 bytes
- Lines
- 28
- 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_bnr2_2_types.hia_css_bnr2_2_param.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __IA_CSS_BNR2_2_HOST_H
#define __IA_CSS_BNR2_2_HOST_H
#include "ia_css_bnr2_2_types.h"
#include "ia_css_bnr2_2_param.h"
extern const struct ia_css_bnr2_2_config default_bnr2_2_config;
void
ia_css_bnr2_2_encode(
struct sh_css_isp_bnr2_2_params *to,
const struct ia_css_bnr2_2_config *from,
size_t size);
#ifndef IA_CSS_NO_DEBUG
void
ia_css_bnr2_2_debug_dtrace(
const struct ia_css_bnr2_2_config *config,
unsigned int level);
#endif
#endif /* __IA_CSS_BNR2_2_HOST_H */
Annotation
- Immediate include surface: `ia_css_bnr2_2_types.h`, `ia_css_bnr2_2_param.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.