drivers/staging/most/dim2/errors.h
Source file repositories/reference/linux-study-clean/drivers/staging/most/dim2/errors.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/most/dim2/errors.h- Extension
.h- Size
- 1055 bytes
- Lines
- 52
- 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
- No C-style include directives detected by the generator.
Detected Declarations
enum dim_errors_t
Annotated Snippet
#ifndef _MOST_DIM_ERRORS_H
#define _MOST_DIM_ERRORS_H
/**
* MOST DIM errors.
*/
enum dim_errors_t {
/** Not an error */
DIM_NO_ERROR = 0,
/** Bad base address for DIM2 IP */
DIM_INIT_ERR_DIM_ADDR = 0x10,
/**< Bad MediaLB clock */
DIM_INIT_ERR_MLB_CLOCK,
/** Bad channel address */
DIM_INIT_ERR_CHANNEL_ADDRESS,
/** Out of DBR memory */
DIM_INIT_ERR_OUT_OF_MEMORY,
/** DIM API is called while DIM is not initialized successfully */
DIM_ERR_DRIVER_NOT_INITIALIZED = 0x20,
/**
* Configuration does not respect hardware limitations
* for isochronous or synchronous channels
*/
DIM_ERR_BAD_CONFIG,
/**
* Buffer size does not respect hardware limitations
* for isochronous or synchronous channels
*/
DIM_ERR_BAD_BUFFER_SIZE,
DIM_ERR_UNDERFLOW,
DIM_ERR_OVERFLOW,
};
#endif /* _MOST_DIM_ERRORS_H */
Annotation
- Detected declarations: `enum dim_errors_t`.
- 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.