drivers/staging/media/atomisp/pci/isp/kernels/ynr/ynr_1.0/ia_css_ynr_param.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/isp/kernels/ynr/ynr_1.0/ia_css_ynr_param.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/isp/kernels/ynr/ynr_1.0/ia_css_ynr_param.h- Extension
.h- Size
- 783 bytes
- Lines
- 42
- 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_ynr_paramsstruct sh_css_isp_yee_params
Annotated Snippet
struct sh_css_isp_ynr_params {
s32 threshold;
s32 gain_all;
s32 gain_dir;
s32 threshold_cb;
s32 threshold_cr;
};
/* YEE (Y Edge Enhancement) */
struct sh_css_isp_yee_params {
s32 dirthreshold_s;
s32 dirthreshold_g;
s32 dirthreshold_width_log2;
s32 dirthreshold_width;
s32 detailgain;
s32 coring_s;
s32 coring_g;
s32 scale_plus_s;
s32 scale_plus_g;
s32 scale_minus_s;
s32 scale_minus_g;
s32 clip_plus_s;
s32 clip_plus_g;
s32 clip_minus_s;
s32 clip_minus_g;
s32 Yclip;
};
#endif /* __IA_CSS_YNR_PARAM_H */
Annotation
- Immediate include surface: `type_support.h`.
- Detected declarations: `struct sh_css_isp_ynr_params`, `struct sh_css_isp_yee_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.