drivers/staging/media/atomisp/pci/hive_isp_css_include/host/fifo_monitor_public.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/hive_isp_css_include/host/fifo_monitor_public.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/hive_isp_css_include/host/fifo_monitor_public.h- Extension
.h- Size
- 2869 bytes
- Lines
- 103
- 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
system_local.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __FIFO_MONITOR_PUBLIC_H_INCLUDED__
#define __FIFO_MONITOR_PUBLIC_H_INCLUDED__
#include "system_local.h"
typedef struct fifo_channel_state_s fifo_channel_state_t;
typedef struct fifo_switch_state_s fifo_switch_state_t;
typedef struct fifo_monitor_state_s fifo_monitor_state_t;
/*! Set a fifo switch multiplex
\param ID[in] FIFO_MONITOR identifier
\param switch_id[in] fifo switch identifier
\param sel[in] fifo switch selector
\return none, fifo_switch[switch_id].sel = sel
*/
STORAGE_CLASS_FIFO_MONITOR_H void fifo_switch_set(
const fifo_monitor_ID_t ID,
const fifo_switch_t switch_id,
const hrt_data sel);
/*! Get a fifo switch multiplex
\param ID[in] FIFO_MONITOR identifier
\param switch_id[in] fifo switch identifier
\return fifo_switch[switch_id].sel
*/
STORAGE_CLASS_FIFO_MONITOR_H hrt_data fifo_switch_get(
const fifo_monitor_ID_t ID,
const fifo_switch_t switch_id);
/*! Read the state of FIFO_MONITOR[ID]
\param ID[in] FIFO_MONITOR identifier
\param state[out] fifo monitor state structure
\return none, state = FIFO_MONITOR[ID].state
*/
void fifo_monitor_get_state(
const fifo_monitor_ID_t ID,
fifo_monitor_state_t *state);
/*! Read the state of a fifo channel
\param ID[in] FIFO_MONITOR identifier
\param channel_id[in] fifo channel identifier
\param state[out] fifo channel state structure
\return none, state = fifo_channel[channel_id].state
*/
void fifo_channel_get_state(
const fifo_monitor_ID_t ID,
const fifo_channel_t channel_id,
fifo_channel_state_t *state);
/*! Read the state of a fifo switch
\param ID[in] FIFO_MONITOR identifier
\param switch_id[in] fifo switch identifier
\param state[out] fifo switch state structure
\return none, state = fifo_switch[switch_id].state
*/
void fifo_switch_get_state(
const fifo_monitor_ID_t ID,
const fifo_switch_t switch_id,
fifo_switch_state_t *state);
/*! Write to a control register of FIFO_MONITOR[ID]
\param ID[in] FIFO_MONITOR identifier
\param reg[in] register index
\param value[in] The data to be written
\return none, FIFO_MONITOR[ID].ctrl[reg] = value
*/
STORAGE_CLASS_FIFO_MONITOR_H void fifo_monitor_reg_store(
const fifo_monitor_ID_t ID,
const unsigned int reg,
const hrt_data value);
/*! Read from a control register of FIFO_MONITOR[ID]
\param ID[in] FIFO_MONITOR identifier
\param reg[in] register index
\param value[in] The data to be written
\return FIFO_MONITOR[ID].ctrl[reg]
Annotation
- Immediate include surface: `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.