drivers/staging/media/sunxi/sun6i-isp/uapi/sun6i-isp-config.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/sunxi/sun6i-isp/uapi/sun6i-isp-config.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/sunxi/sun6i-isp/uapi/sun6i-isp-config.h- Extension
.h- Size
- 899 bytes
- Lines
- 44
- 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
linux/types.h
Detected Declarations
struct sun6i_isp_params_config_bayerstruct sun6i_isp_params_config_bdnfstruct sun6i_isp_params_config
Annotated Snippet
struct sun6i_isp_params_config_bayer {
__u16 offset_r;
__u16 offset_gr;
__u16 offset_gb;
__u16 offset_b;
__u16 gain_r;
__u16 gain_gr;
__u16 gain_gb;
__u16 gain_b;
};
struct sun6i_isp_params_config_bdnf {
__u8 in_dis_min;
__u8 in_dis_max;
__u8 coefficients_g[7];
__u8 coefficients_rb[5];
};
struct sun6i_isp_params_config {
__u32 modules_used;
struct sun6i_isp_params_config_bayer bayer;
struct sun6i_isp_params_config_bdnf bdnf;
};
#endif /* _UAPI_SUN6I_ISP_CONFIG_H */
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct sun6i_isp_params_config_bayer`, `struct sun6i_isp_params_config_bdnf`, `struct sun6i_isp_params_config`.
- 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.