drivers/staging/media/atomisp/pci/hive_isp_css_common/host/dma_private.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/hive_isp_css_common/host/dma_private.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/hive_isp_css_common/host/dma_private.h- Extension
.h- Size
- 845 bytes
- Lines
- 34
- 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
dma_public.hdevice_access.hassert_support.h
Detected Declarations
function Copyrightfunction dma_reg_load
Annotated Snippet
#ifndef __DMA_PRIVATE_H_INCLUDED__
#define __DMA_PRIVATE_H_INCLUDED__
#include "dma_public.h"
#include "device_access.h"
#include "assert_support.h"
STORAGE_CLASS_DMA_C void dma_reg_store(const dma_ID_t ID,
const unsigned int reg,
const hrt_data value)
{
assert(ID < N_DMA_ID);
assert(DMA_BASE[ID] != (hrt_address) - 1);
ia_css_device_store_uint32(DMA_BASE[ID] + reg * sizeof(hrt_data), value);
}
STORAGE_CLASS_DMA_C hrt_data dma_reg_load(const dma_ID_t ID,
const unsigned int reg)
{
assert(ID < N_DMA_ID);
assert(DMA_BASE[ID] != (hrt_address) - 1);
return ia_css_device_load_uint32(DMA_BASE[ID] + reg * sizeof(hrt_data));
}
#endif /* __DMA_PRIVATE_H_INCLUDED__ */
Annotation
- Immediate include surface: `dma_public.h`, `device_access.h`, `assert_support.h`.
- Detected declarations: `function Copyright`, `function dma_reg_load`.
- 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.