drivers/staging/media/atomisp/pci/isp/kernels/tdf/tdf_1.0/ia_css_tdf_param.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/isp/kernels/tdf/tdf_1.0/ia_css_tdf_param.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/isp/kernels/tdf/tdf_1.0/ia_css_tdf_param.h- Extension
.h- Size
- 751 bytes
- Lines
- 36
- 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.hvmem.h
Detected Declarations
struct ia_css_isp_tdf_vmem_paramsstruct ia_css_isp_tdf_dmem_params
Annotated Snippet
struct ia_css_isp_tdf_vmem_params {
VMEM_ARRAY(pyramid, ISP_VEC_NELEMS);
VMEM_ARRAY(threshold_flat, ISP_VEC_NELEMS);
VMEM_ARRAY(threshold_detail, ISP_VEC_NELEMS);
};
struct ia_css_isp_tdf_dmem_params {
s32 Epsilon_0;
s32 Epsilon_1;
s32 EpsScaleText;
s32 EpsScaleEdge;
s32 Sepa_flat;
s32 Sepa_Edge;
s32 Blend_Flat;
s32 Blend_Text;
s32 Blend_Edge;
s32 Shading_Gain;
s32 Shading_baseGain;
s32 LocalY_Gain;
s32 LocalY_baseGain;
};
#endif /* __IA_CSS_TDF_PARAM_H */
Annotation
- Immediate include surface: `type_support.h`, `vmem.h`.
- Detected declarations: `struct ia_css_isp_tdf_vmem_params`, `struct ia_css_isp_tdf_dmem_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.