drivers/staging/media/atomisp/pci/isp/kernels/bnr/bnr2_2/ia_css_bnr2_2_param.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/isp/kernels/bnr/bnr2_2/ia_css_bnr2_2_param.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/isp/kernels/bnr/bnr2_2/ia_css_bnr2_2_param.h- Extension
.h- Size
- 837 bytes
- Lines
- 40
- 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
Detected Declarations
struct sh_css_isp_bnr2_2_params
Annotated Snippet
struct sh_css_isp_bnr2_2_params {
s32 d_var_gain_r;
s32 d_var_gain_g;
s32 d_var_gain_b;
s32 d_var_gain_slope_r;
s32 d_var_gain_slope_g;
s32 d_var_gain_slope_b;
s32 n_var_gain_r;
s32 n_var_gain_g;
s32 n_var_gain_b;
s32 n_var_gain_slope_r;
s32 n_var_gain_slope_g;
s32 n_var_gain_slope_b;
s32 dir_thres;
s32 dir_thres_w;
s32 var_offset_coef;
s32 dir_gain;
s32 detail_gain;
s32 detail_gain_divisor;
s32 detail_level_offset;
s32 d_var_th_min;
s32 d_var_th_max;
s32 n_var_th_min;
s32 n_var_th_max;
};
#endif /* __IA_CSS_BNR2_2_PARAM_H */
Annotation
- Immediate include surface: `type_support.h`.
- Detected declarations: `struct sh_css_isp_bnr2_2_params`.
- 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.