drivers/staging/media/atomisp/pci/hive_isp_css_common/host/fifo_monitor_local.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/hive_isp_css_common/host/fifo_monitor_local.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/hive_isp_css_common/host/fifo_monitor_local.h- Extension
.h- Size
- 2213 bytes
- Lines
- 92
- 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.hfifo_monitor_global.hhive_isp_css_defs.h
Detected Declarations
struct fifo_channel_state_sstruct fifo_switch_state_sstruct fifo_monitor_state_s
Annotated Snippet
struct fifo_channel_state_s {
bool src_valid;
bool fifo_accept;
bool fifo_valid;
bool sink_accept;
};
/* The switch is tri-state */
struct fifo_switch_state_s {
bool is_none;
bool is_isp;
bool is_sp;
};
struct fifo_monitor_state_s {
struct fifo_channel_state_s fifo_channels[N_FIFO_CHANNEL];
struct fifo_switch_state_s fifo_switches[N_FIFO_SWITCH];
};
#endif /* __FIFO_MONITOR_LOCAL_H_INCLUDED__ */
Annotation
- Immediate include surface: `type_support.h`, `fifo_monitor_global.h`, `hive_isp_css_defs.h`.
- Detected declarations: `struct fifo_channel_state_s`, `struct fifo_switch_state_s`, `struct fifo_monitor_state_s`.
- 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.