drivers/staging/media/atomisp/pci/isp/kernels/iterator/iterator_1.0/ia_css_iterator.host.c
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/isp/kernels/iterator/iterator_1.0/ia_css_iterator.host.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/isp/kernels/iterator/iterator_1.0/ia_css_iterator.host.c- Extension
.c- Size
- 2579 bytes
- Lines
- 69
- 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_iterator.host.hia_css_frame_public.hia_css_binary.hia_css_err.hia_css_isp_configs.h
Detected Declarations
function ia_css_iterator_configfunction ia_css_iterator_configure
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* Support for Intel Camera Imaging ISP subsystem.
* Copyright (c) 2015, Intel Corporation.
*/
#include "ia_css_iterator.host.h"
#include "ia_css_frame_public.h"
#include "ia_css_binary.h"
#include "ia_css_err.h"
#define IA_CSS_INCLUDE_CONFIGURATIONS
#include "ia_css_isp_configs.h"
static const struct ia_css_iterator_configuration default_config = {
.input_info = (struct ia_css_frame_info *)NULL,
};
void
ia_css_iterator_config(
struct sh_css_isp_iterator_isp_config *to,
const struct ia_css_iterator_configuration *from,
unsigned int size)
{
(void)size;
ia_css_frame_info_to_frame_sp_info(&to->input_info, from->input_info);
ia_css_frame_info_to_frame_sp_info(&to->internal_info, from->internal_info);
ia_css_frame_info_to_frame_sp_info(&to->output_info, from->output_info);
ia_css_frame_info_to_frame_sp_info(&to->vf_info, from->vf_info);
ia_css_resolution_to_sp_resolution(&to->dvs_envelope, from->dvs_envelope);
}
int ia_css_iterator_configure(const struct ia_css_binary *binary,
const struct ia_css_frame_info *in_info)
{
struct ia_css_frame_info my_info = IA_CSS_BINARY_DEFAULT_FRAME_INFO;
struct ia_css_iterator_configuration config = default_config;
config.input_info = &binary->in_frame_info;
config.internal_info = &binary->internal_frame_info;
config.output_info = &binary->out_frame_info[0];
config.vf_info = &binary->vf_frame_info;
config.dvs_envelope = &binary->dvs_envelope;
/* Use in_info iso binary->in_frame_info.
* They can differ in padded width in case of scaling, e.g. for capture_pp.
* Find out why.
*/
if (in_info)
config.input_info = in_info;
if (binary->out_frame_info[0].res.width == 0)
config.output_info = &binary->out_frame_info[1];
my_info = *config.output_info;
config.output_info = &my_info;
/* we do this only for preview pipe because in fill_binary_info function
* we assign vf_out res to out res, but for ISP internal processing, we need
* the original out res. for video pipe, it has two output pins --- out and
* vf_out, so it can keep these two resolutions already. */
if (binary->info->sp.pipeline.mode == IA_CSS_BINARY_MODE_PREVIEW &&
binary->vf_downscale_log2 > 0) {
/* TODO: Remove this after preview output decimation is fixed
* by configuring out&vf info files properly */
my_info.padded_width <<= binary->vf_downscale_log2;
my_info.res.width <<= binary->vf_downscale_log2;
my_info.res.height <<= binary->vf_downscale_log2;
}
return ia_css_configure_iterator(binary, &config);
}
Annotation
- Immediate include surface: `ia_css_iterator.host.h`, `ia_css_frame_public.h`, `ia_css_binary.h`, `ia_css_err.h`, `ia_css_isp_configs.h`.
- Detected declarations: `function ia_css_iterator_config`, `function ia_css_iterator_configure`.
- 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.