drivers/staging/media/atomisp/pci/hive_isp_css_include/host/input_formatter_public.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/hive_isp_css_include/host/input_formatter_public.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/hive_isp_css_include/host/input_formatter_public.h- Extension
.h- Size
- 3182 bytes
- Lines
- 108
- 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.
Dependency Surface
type_support.hsystem_local.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __INPUT_FORMATTER_PUBLIC_H_INCLUDED__
#define __INPUT_FORMATTER_PUBLIC_H_INCLUDED__
#include <type_support.h>
#include "system_local.h"
/*! Reset INPUT_FORMATTER[ID]
\param ID[in] INPUT_FORMATTER identifier
\return none, reset(INPUT_FORMATTER[ID])
*/
void input_formatter_rst(
const input_formatter_ID_t ID);
/*! Set the blocking mode of INPUT_FORMATTER[ID]
\param ID[in] INPUT_FORMATTER identifier
\param enable[in] blocking enable flag
\use
- In HW, the capture unit will deliver an infinite stream of frames,
the input formatter will synchronise on the first SOF. In simulation
there are only a fixed number of frames, presented only once. By
enabling blocking the inputformatter will wait on the first presented
frame, thus avoiding race in the simulation setup.
\return none, INPUT_FORMATTER[ID].blocking_mode = enable
*/
void input_formatter_set_fifo_blocking_mode(
const input_formatter_ID_t ID,
const bool enable);
/*! Return the data alignment of INPUT_FORMATTER[ID]
\param ID[in] INPUT_FORMATTER identifier
\return alignment(INPUT_FORMATTER[ID].data)
*/
unsigned int input_formatter_get_alignment(
const input_formatter_ID_t ID);
/*! Read the source switch state into INPUT_FORMATTER[ID]
\param ID[in] INPUT_FORMATTER identifier
\param state[out] input formatter switch state structure
\return none, state = INPUT_FORMATTER[ID].switch_state
*/
void input_formatter_get_switch_state(
const input_formatter_ID_t ID,
input_formatter_switch_state_t *state);
/*! Read the control registers of INPUT_FORMATTER[ID]
\param ID[in] INPUT_FORMATTER identifier
\param state[out] input formatter state structure
\return none, state = INPUT_FORMATTER[ID].state
*/
void input_formatter_get_state(
const input_formatter_ID_t ID,
input_formatter_state_t *state);
/*! Read the control registers of bin copy INPUT_FORMATTER[ID]
\param ID[in] INPUT_FORMATTER identifier
\param state[out] input formatter state structure
\return none, state = INPUT_FORMATTER[ID].state
*/
void input_formatter_bin_get_state(
const input_formatter_ID_t ID,
input_formatter_bin_state_t *state);
/*! Write to a control register of INPUT_FORMATTER[ID]
\param ID[in] INPUT_FORMATTER identifier
\param reg_addr[in] register byte address
\param value[in] The data to be written
\return none, INPUT_FORMATTER[ID].ctrl[reg] = value
*/
STORAGE_CLASS_INPUT_FORMATTER_H void input_formatter_reg_store(
const input_formatter_ID_t ID,
const hrt_address reg_addr,
const hrt_data value);
/*! Read from a control register of INPUT_FORMATTER[ID]
Annotation
- Immediate include surface: `type_support.h`, `system_local.h`.
- 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.