drivers/staging/media/atomisp/pci/hive_isp_css_include/host/isys_irq_public.h

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/atomisp/pci/hive_isp_css_include/host/isys_irq_public.h

Extension

.h

Size

770 bytes

Lines

31

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

• isys_irq_global.h
• isys_irq_local.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __ISYS_IRQ_PUBLIC_H__
#define __ISYS_IRQ_PUBLIC_H__

#include "isys_irq_global.h"
#include "isys_irq_local.h"


void isys_irqc_state_get(const isys_irq_ID_t	isys_irqc_id,
			 isys_irqc_state_t	*state);

void isys_irqc_state_dump(const isys_irq_ID_t	isys_irqc_id,
			  const isys_irqc_state_t *state);

void isys_irqc_reg_store(const isys_irq_ID_t	isys_irqc_id,
			 const unsigned int	reg_idx,
			 const hrt_data		value);

hrt_data isys_irqc_reg_load(const isys_irq_ID_t	isys_irqc_id,
			    const unsigned int	reg_idx);

void isys_irqc_status_enable(const isys_irq_ID_t isys_irqc_id);


#endif	/* __ISYS_IRQ_PUBLIC_H__ */

Annotation

• Immediate include surface: `isys_irq_global.h`, `isys_irq_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.