drivers/staging/media/atomisp/pci/hive_isp_css_common/hmem_global.h
Source file repositories/reference/linux-study-clean/drivers/staging/media/atomisp/pci/hive_isp_css_common/hmem_global.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/atomisp/pci/hive_isp_css_common/hmem_global.h- Extension
.h- Size
- 990 bytes
- Lines
- 38
- 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.hisp.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __HMEM_GLOBAL_H_INCLUDED__
#define __HMEM_GLOBAL_H_INCLUDED__
#include <type_support.h>
#define IS_HMEM_VERSION_1
#include "isp.h"
/*
#define ISP_HIST_ADDRESS_BITS 12
#define ISP_HIST_ALIGNMENT 4
#define ISP_HIST_COMP_IN_PREC 12
#define ISP_HIST_DEPTH 1024
#define ISP_HIST_WIDTH 24
#define ISP_HIST_COMPONENTS 4
*/
#define ISP_HIST_ALIGNMENT_LOG2 2
#define HMEM_SIZE_LOG2 (ISP_HIST_ADDRESS_BITS - ISP_HIST_ALIGNMENT_LOG2)
#define HMEM_SIZE ISP_HIST_DEPTH
#define HMEM_UNIT_SIZE (HMEM_SIZE / ISP_HIST_COMPONENTS)
#define HMEM_UNIT_COUNT ISP_HIST_COMPONENTS
#define HMEM_RANGE_LOG2 ISP_HIST_WIDTH
#define HMEM_RANGE BIT(HMEM_RANGE_LOG2)
typedef u32 hmem_data_t;
#endif /* __HMEM_GLOBAL_H_INCLUDED__ */
Annotation
- Immediate include surface: `type_support.h`, `isp.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.